Re: On Contributing To Emacs

[Stefan Kangas]

Ihor Radchenko <yantar92@gmail.com> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Our core packages can be released straight from master to GNU ELPA
>> within 24 hours.  All you need to do, once it is set up (which in itself
>> is trivial), is to bump the version header.  This is already the case
>> with for example flymake.el and python.el.
>
> Could this information be added to "GNU ELPA" section of the CONTRIBUTE
> file? The current contents of the section is rather confusing:
>
> "This repository does not contain the Emacs Lisp package archive
> (elpa.gnu.org).  See admin/notes/elpa for how to access the GNU ELPA
> repository."

How is this?

diff --git a/CONTRIBUTE b/CONTRIBUTE
index 7c3421ed75..f2d161e808 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -372,6 +372,14 @@ This repository does not contain the Emacs Lisp
package archive
 (elpa.gnu.org).  See admin/notes/elpa for how to access the GNU ELPA
 repository.

+Some packages are so-called "core" packages.  The GNU ELPA scripts
+will pick them up from the Emacs master branch and release them as
+packages periodically; a new version is packaged when their "Version"
+comment header is updated.  Normally a new package is released within
+24 hours after bumping the version on the Emacs master branch.  An
+examples is lisp/progmodes/python.el, which is released as the "python"
+package at: https://elpa.gnu.org/packages/python.html
+
 ** Understanding Emacs internals

 The best way to understand Emacs internals is to read the code.  Some