Merge from emacs-24; up to 2013-01-03T02:31:36Z!rgm@gnu.org
[bpt/emacs.git] / admin / notes / elpa
CommitLineData
eea682b6
CY
1NOTES ON THE EMACS PACKAGE ARCHIVE
2
7763d67c
SM
3The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git
4repository named "elpa", hosted on Savannah. To check it out:
eb8694ee 5
7763d67c 6 git clone git://bzr.sv.gnu.org/emacs/elpa
7f0869bd 7 cd elpa
7763d67c 8 git remote set-url --push origin git+ssh://bzr.sv.gnu.org/srv/git/emacs/elpa
7f0869bd 9 [create task branch for edits, etc.]
eb8694ee 10
7763d67c
SM
11Changes to this branch propagate to elpa.gnu.org via a "deployment" script run
12daily. This script (which is kept in elpa/admin/update-archive.sh) generates
13the content visible at http://elpa.gnu.org/packages.
eb8694ee 14
7763d67c
SM
15A new package is released as soon as the "version number" of that package is
16changed. So you can use `elpa' to work on a package without fear of releasing
17those changes prematurely. And once the code is ready, just bump the
18version number to make a new release of the package.
eb8694ee 19
7f0869bd
CY
20It is easy to use the elpa branch to deploy a "local" copy of the
21package archive. For details, see the README file in the elpa branch.