Auto-tools/Projects/Mozmill/Release: Difference between revisions

Auto-tools/Projects/Mozmill/Release (view source)

105 bytes added , 3 October 2011

cleanup --- in progress

947

edits

@@ Line 1: / Line 1: @@
 Releasing Mozmill has a lot of moving parts.  Here's how it's done.
-= Releasing For Real =
+(See https://bugzilla.mozilla.org/show_bug.cgi?id=691368 for the bad page title)
-# Release to Pypi
-# Release to AMO
+= Bump the Version Numbers in the Source =
-# Release to Mozilla-central
+Versions are recorded in the python package setup.py files, and the
+extension install.rdf files (for jsbridge and mozmill).  In addition,
+the python package dependencies should be appropriately bumped as
+well.
+In order to bump the versions, it is recommended that you use the
+version bumping script:
+https://github.com/mozautomation/mozmill/blob/master/versionbump.py
+Using --help to see the options for this script.
 = Releasing a Preview Release (aka Release to PyPi) =
-For previews (beta, alpha, rc etc) it's pretty easy.  You just send it up to pypi because bothering the AMO Editors for review of a pre-release addon really wastes their time.  The one exception to this is for major releases, it might be good to get AMO editor feedback early.  But in general, for these releases, we just go to pypi.  It's done like so:
 # Bump your version: git checkout -b versionbump (do this from your dev branch for the release)