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

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

246 bytes removed , 3 October 2011

947

edits

@@ Line 19: / Line 19: @@
 = Releasing a Preview Release (aka Release to PyPi) =
-# Bump your version: git checkout -b versionbump (do this from your dev branch for the release)
-# Change all the setup.py/install.rdf's to have the proper <blah>rcX version where X is your rc number.  For betas, use 'beta' etc.  Pretty straightforward.
 # Make a bug and attach the patch from 2 for review.  This is a good step just to ensure we don't miss anything.  Leave that bug open until we release so that you don't have to have a new bug for every silly version bump (i.e. rc1, then rc2 etc)
 # Once you have review, commit your change to the development branch.
@@ Line 26: / Line 24: @@
 # Verify that the packages have been uploaded correctly by updating from an older version of Mozmill and a new installation
-'''Note:''' For step 5, you'll have to have a key registered with [http://pypi.python.org pypi] and be listed as a maintainer of the pypi packages in order for the upload step to work.  If you need that access for some reason, let harth or ctalbert know.
+'''Note:''' To upload to PyPI, you'll have to have a key registered with [http://pypi.python.org pypi] and be listed as a maintainer of the pypi packages in order for the upload step to work.  If you need that access for some reason, let harth or ctalbert know.
 = Release to AMO =