Changes between Version 3 and Version 4 of Bitten Dev/Release Check List

Timestamp:

Sep 10, 2009, 1:26:14 PM (15 years ago)

Author:

osimons

Comment:

More release information.

Bitten Dev/Release Check List

@@ -3 +3 @@
 == Prepare source for release ==
 
+Verify:
  * Build docs with command: `./setup.py build_doc`
- * Update version in setup.py
+ * Run unittests on all major platforms
+
+Make and commit changes:
+
+ * Update version in `setup.py`
  * Drop `[egg_info]` section `setup.cfg`
- * Update `ChangeLog` with release information and changes.
+ * Update `ChangeLog` with release information and changes
+ * Before major releases:
+   * `svn copy trunk -> /branches/<major>.x`
+   * Initialize merge-tracking from trunk to new branch
 
-== Major releases ==
-
- * svn copy trunk -> /branches/<major>.x
-
-== Minor releases and betas ==
+== Tag release ==
 
  * svn copy /branches/<major>.x -> /tags/<major>.<minor><beta?>
+ * Commit message should contain a link to `[milestone:<major><minor>]` if not beta.
 
-== After release ==
+== Adjust source trees ==
 
- * Reset version information in `setup.cfg` to new next version + `dev`
+Make and commit changes:
+
+ * Reset version information in `setup.py` to new next version + add back `[egg_info]` section
+ * Add new empty section in `ChangeLog` for coming version
+ * If `ChangeLog` changed in branch, also update in trunk
+
+== Make releases ==
 
  * Upload to Downloads and FTP installers in following formats and versions:
@@ -25 +36 @@
    * py25.egg
    * py24.egg
+
+== Announce ==
+
+Write an email to bitten mailing list.
+
+== Questions... ==
+ * What about pypi entries?
+ * Do we prepare releases for both Bitten and Bitten-Slave?
+