|
Revision 503, 1.2 kB
(checked in by ged, 2 years ago)
|
|
update release process to include check of API docs
|
| Line | |
|---|
| 1 | How to make a release: |
|---|
| 2 | |
|---|
| 3 | - svn up |
|---|
| 4 | - change version in CHANGES, add release date and link to upgrade notes if any |
|---|
| 5 | - change version in __version__ (elixir/__init__.py) |
|---|
| 6 | - change version in setup.py |
|---|
| 7 | - change version in setup.cfg (trac link) |
|---|
| 8 | - make sure API doc generates properly: apydia -v -c setup.cfg |
|---|
| 9 | - commit |
|---|
| 10 | |
|---|
| 11 | - make tag in subversion |
|---|
| 12 | "svn copy http://elixir.ematia.de/svn/elixir/trunk |
|---|
| 13 | http://elixir.ematia.de/svn/elixir/tags/%s" % version |
|---|
| 14 | |
|---|
| 15 | - build tar.gz, egg for 2.4 and 2.5 and send them to pypi. |
|---|
| 16 | On my system (Unbuntu gutsy): |
|---|
| 17 | python2.4 setup.py egg_info -RDb "" register bdist_egg upload |
|---|
| 18 | python2.5 setup.py egg_info -RDb "" sdist bdist_egg upload |
|---|
| 19 | |
|---|
| 20 | or, you could also set an alias up like this: |
|---|
| 21 | python setup.py alias -u release egg_info -RDb "" |
|---|
| 22 | |
|---|
| 23 | On older systems, you might need to upload the files manually to Pypi. |
|---|
| 24 | |
|---|
| 25 | - add version to the trac, mark milestone as completed |
|---|
| 26 | |
|---|
| 27 | - announce release on our news page (link to CHANGES) |
|---|
| 28 | |
|---|
| 29 | - announce release on those lists: |
|---|
| 30 | - Elixir <sqlelixir@googlegroups.com> |
|---|
| 31 | - SQLAlchemy <sqlalchemy@googlegroups.com> |
|---|
| 32 | - TurboGears <turbogears@googlegroups.com> |
|---|
| 33 | - Python announce <python-announce-list@python.org> |
|---|
| 34 | |
|---|
| 35 | - announce it on freshmeat |
|---|
