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

← Older edit

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

Revision as of 06:11, 4 October 2011

98 bytes removed , 4 October 2011

m

moved Auto-tools/Projects/Momzill/Release to Auto-tools/Projects/Mozmill/Release

Whimboo

canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,754

edits

@@ Line 3: / Line 3: @@
 (See https://bugzilla.mozilla.org/show_bug.cgi?id=691368 for the bad page title)
-= Bump the Version Numbers in the Source =
+== Bump the Version Numbers in the Source ==
 Versions are recorded in the python package setup.py files, and the
@@ Line 16: / Line 16: @@
 Using --help to see the options for this script.
+Make a bug and attach the patch for review.
-= Releasing a Preview Release (aka Release to PyPi) =
+== Tag the Version ==
-# Bump your version: git checkout -b versionbump (do this from your dev branch for the release)
+Once the versions are bumped and committed to
-# 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.
+https://github.com/mozautomation/mozmill , the branch should be tagged
-# 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)
+with the appropriate version.  As an example, for the hotfix-1.5
-# Once you have review, commit your change to the development branch.
+branch ( https://github.com/mozautomation/mozmill/tree/hotfix-1.5 ),
-# Go into each directory (mozrunner/mozmill/jsbridge) and issue the following command: python setup.py sdist upload
+the process looks like this:
-# 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.
+ git pull --tags mozauto hotfix-1.5
+ git tag
+ git tag 1.5.5
+ git push --tags mozauto hotfix-1.5
+== Release to PyPi ==
+Go into each directory (mozrunner/mozmill/jsbridge) and upload the package to pypi:
+ for i in mozrunner mozmill jsbridge; do cd $i; python setup.py sdist upload; cd ..; done
+'''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 jhammel or ctalbert know.
+== Release to AMO ==
+https://addons.mozilla.org/en-US/firefox/addon/mozmill/ should be
+updated for the latest mozmill version.
-= Release to AMO =
 # Once you have a final version, cd into mozmill/mozmill/mozmill/extension
 # Run: ant -f build.xml (this builds the extension)
 # Log into your AMO account (assuming you are an owner of mozmill on AMO), upload the new extension and fill out the required forms on AMO for it.