1 =============================
2 Docutils_ Release Procedure
3 =============================
5 :Authors: David Goodger; Lea Wiemann; open to all Docutils developers
6 :Contact: docutils-develop@lists.sourceforge.net
9 :Copyright: This document has been placed in the public domain.
11 .. _Docutils: http://docutils.sourceforge.net/
13 Assumptions and their failure
14 -----------------------------
16 On the test machine python2.4, 2.5, 2.6, 2.7 and 3.2, 3.3, and 3.4
18 Some in /usr/ some under /usr/local.
20 Assumption: If python2.6 is in /usr/bin/ than site-packages is under
21 /usr/local/lib/python2.6.
25 * python2.7 is here /usr/bin/python2.7.
26 * in /usr/lib are python2.7, pymodules and pyshared.
28 in /usr/lib/python2.7 no site-packages directory even after installation
31 in /usr/local/lib/python2.7 are dist-packages site-packages.
33 site-packages is empty.
35 docutils is installed under dist-packages.
37 pymodules has a python2.7 directory.
42 Prerelease: test/notify sphinx.
44 Note on numbering (Feature Request #50)
46 PEP 440 specifies how release version are understood by pip and other tools.
48 The last released package of docutils was in 2014.
50 If you install the version from Source it will not be overriden by version
51 0.13 when it is eventaully released.
53 As folks have installed 0.13 from indeterminate source versions the current
54 version should be incremented as to allow pip to overrite a 0.13 snapshot
55 when the next official release.
57 Please increment and switch the version in setup.py to be a pre-release. e.g.
60 When a version is tagged it should be changed to a non pre release and then
61 in the next commit incremented to the next expected version but with a pre
65 0.13.1 -> when tagged for release
66 0.13.2a -> new head after release
68 Additionally snapshots can be marked with the .devXXX nominclature.
70 These can then all be pushed to pypi.python.org and by default pip will install the latest release unless explicitly requested via the --pre flag or a version specifier docutils>=0.13.1a
72 REWORK FOR SOURCEFORGE REPO
74 Steps in boldface text are *not* covered by the release script at
75 sandbox/infrastructure/release.sh. "Not covered" means that you aren't even
78 .. Note:: This document does not cover branching and tagging, but the
81 .. Note:: You may want to use ReleaseForge_ instead of using
82 SourceForge's file release system.
84 .. _ReleaseForge: http://releaseforge.sourceforge.net/
87 * **On the Docutils-develop mailing list, announce that the release is
88 going to be made, update the release notes and ask for additions.**
90 Consult HISTORY.TXT for changes.
92 * **Announce a check-in freeze on Docutils-develop.**
94 Call ``sandbox/infrastructure/release.sh new_version svn_version``.
95 For details see the script.
97 ``new_version`` is the current version, status will change from ``repository`` to
98 ``release``. ``svn_version`` is the version after release.
100 .. Note:: *BUG* test tarball requires root password, but it is possible to skip
101 this stage interactively, and testing should be done before release.
103 * Change ``__version_details__`` in docutils/docutils/__init__.py to
104 "release" (from "repository").
106 * Check the _`version number` in the following files, should be already
110 + docutils/docutils/__init__.py
111 + docutils/test/functional/expected/* ("Generator: Docutils X.Y.Z")
112 + docutils/README.txt
115 * Close the "Changes Since ..." section in docutils/HISTORY.txt.
117 * Clear/unset the PYTHONPATH environment variable.
119 * Create the release tarball:
121 (a) Create a new empty directory and ``cd`` into it.
123 (b) Get a clean snapshot of the main tree::
125 svn export svn://svn.code.sf.net/p/docutils/code/trunk/docutils
127 or via the [Download Snapshot] button at
128 http://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils/
130 (c) Use Distutils to create the release tarball::
133 python setup.py sdist
135 .. note:: PyPI recommends to `create and upload wheels`_ in addition to
138 * Expand and _`install` the release tarball in isolation:
140 (a) Expand the tarball in a new location, not over any existing
143 (b) Remove the old installation from site-packages (including
144 roman.py, and optparse.py, textwrap.py).
146 "remove" might fail, see _`Assumptions and their failure`
148 Install from expanded directory::
151 python setup.py install
153 The "install" command may require root permissions.
155 (c) Repeat step b) for all supported Python versions.
157 * Run the _`test suite` from the expanded archive directory with all
158 supported Python versions on all available platforms (GNU/Linux, Mac
161 cd test ; python -u alltests.py
163 * Add a directory X.Y.Z (where X.Y.Z is the current version number
164 of Docutils) in the webroot (i.e. the ``htdocs/`` directory).
165 Put all documentation files into it::
172 find -name test -type d -prune -o -name \*.css -print0 \
173 -o -name \*.html -print0 -o -name \*.txt -print0 \
174 | tar -cjvf docutils-docs.tar.bz2 -T - --null
175 scp docutils-docs.tar.bz2 <username>@shell.sourceforge.net:
177 Now log in to shell.sourceforge.net and::
179 cd /home/groups/d/do/docutils/htdocs/
180 mkdir -m g+rwxs X.Y.Z
182 tar -xjvf ~/docutils-docs.tar.bz2
183 rm ~/docutils-docs.tar.bz2
185 * Upload the release tarball, release.sh tries with scp.
187 * Access the _`file release system` on SourceForge (Admin
190 ``https://sourceforge.net/projects/docutils/files/docutils/``
192 * change into the released version's directory
193 * click ``(i)`` button of the tar.gz-file
194 * select as default download for all operating systems.
196 * Submit a notification on project news.
198 * For verifying the integrity of the release, download the release
199 tarball (you may need to wait up to 30 minutes), install_ it, and
200 re-run the `test suite`_.
202 * Register with PyPI (``python setup.py register``).
204 Set the download-url so eggs can access older releases.
206 _`create and upload wheels`:
208 * The `Python Packaging User Guide` recommends to provide `wheels`_ [#]_ in
209 addition to the source tarball.
211 .. [#] A Built Distribution format introduced by pypa:PEP427s, which is
212 intended to replace the Egg format. Wheel is currently supported by
215 .. _wheels: https://packaging.python.org/en/latest/distributing.html#wheels
216 __ https://pypi.python.org/pypi/pip/
218 See also `feature request 43
219 <https://sourceforge.net/p/docutils/feature-requests/43/>`__
221 For current Docutils, this would mean `pure Python wheels`__ for Python 2
224 __ https://packaging.python.org/en/latest/distributing.html#pure-python-wheels
227 + Eventually install the `pip <https://pypi.python.org/pypi/pip/>`__` and
228 `wheel <https://pypi.python.org/pypi/wheel/>`__ packages.
232 For the default Python version:
234 - From release at PyPI ::
238 - From working directory's sub-directory "docutils" ::
240 pip wheel ./docutils/
242 Under Debian, the default Python version is 2.7 and the wheel is usable
243 for all 2.x versions supported by Docutils and
244 the command ``pip3 wheel docutils`` generates a wheel suitable for Py3k.
248 __ https://packaging.python.org/en/latest/distributing.html#upload-your-distributions
251 * Restore ``__version_details__`` in docutils/docutils/__init__.py to
252 "repository" (from "release").
254 * Bump the `version number`_ again.
256 * Add a new empty section "Changes Since ..." in HISTORY.txt.
258 * Update the web page (web/index.txt).
260 * Run docutils-update on the server.
262 * **Run alltests.py with svn version**
264 * **Send announcement email to:**
266 * docutils-develop@lists.sourceforge.net (also announcing the end of
268 * docutils-users@lists.sourceforge.net
270 * python-announce@python.org
272 * **Add a SourceForge News item, with title "Docutils X.Y.Z released"
273 and containing the release tarball's download URL.**
275 **Mark as default download for all platforms.**
277 * **Register with freecode.** Add a new release for the
278 `Docutils project`__. (freecode is freshmeat.net's new name)
280 __ http://freecode.com/projects/docutils/
282 * **build a wheel** at least for python3::
286 This builds the wheel by downloading the new release from pypi.
288 Upload the wheel to pypi.
290 Question: Can we have an tar.gz (distutil) and a py2-wheel and a py3-wheel
291 on pypi and will installers select the correct files ?
297 indent-tabs-mode: nil
298 sentence-end-double-space: t