Changes between Version 11 and Version 12 of MakingReleases

Timestamp:

08/26/07 02:39:49 (6 years ago)

Author:

jarrod.millman

Comment:

--

MakingReleases

@@ -3 +3 @@
 As of August 2007, we will create a stable branch every 3 months.  Development will continue on the trunk and we will tag off the branch only as needed to address bugs.  For more specific details about the roadmap see milestone:0.6, milestone:0.7, ...
 
-Version numbering: 
 
+To make a "release" of !SciPy, the release manager should follow these steps:
+
+= Prepare for upcoming release =
+ 1. Announce upcoming release on the developer's list.
+  * introduce a soft-freeze
+ 1. Create a release branch (if none exists).
+   * {{{svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/branches/<version> -m "Create a release branch."}}}
+   * increment version number in {{{trunk/scipy/version.py}}}
+
+Understanding the version numbering:
 || 0.6.0 || a major stable releases ||
 || 0.6.X || the first maintenance releases (bugfixes only) ||
@@ -10 +19 @@
 || 0.7.0.dev3532   || version 3532 of the development trunk leading to 0.7 ||
 
-
-= Prepare for upcoming release =
- 1. Announce upcoming release on the developer's list.
- 1. Create a release branch (if none exists).
-   * {{{svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/branches/<version> -m "Create a release branch."}}}
-   * Increment the version number in {{{trunk/scipy/version.py}}}
-
 = Review the state of the branch =
  1. Make sure the current trunk builds a package correctly:
-{{{
-python setup.py bdist
-python setup.py sdist
-}}}
-
-
+ 1. All tests should pass.
+ 1. 
 
 = Create the release tag =