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

From MozillaWiki
Jump to navigation Jump to search
(overall fixes)
Line 3: Line 3:
(See https://bugzilla.mozilla.org/show_bug.cgi?id=691368 for the bad page title)
(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
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.
Using --help to see the options for this script.


Make a bug and attach the patch for review.


= Release to PyPi =
== Release to PyPi ==


# 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)
Go into each directory (mozrunner/mozmill/jsbridge) and upload the package to pypi:  
# Once you have review, commit your change to the development branch.
# Go into each directory (mozrunner/mozmill/jsbridge) and issue the following command: python setup.py sdist upload
# Verify that the packages have been uploaded correctly by updating from an older version of Mozmill and a new installation


'''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.
for i in mozrunner mozmill jsbridge; do cd $i; python setup.py sdist upload; cd ..; done


= Release to AMO =
'''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 ==
# Once you have a final version, cd into mozmill/mozmill/mozmill/extension
# Once you have a final version, cd into mozmill/mozmill/mozmill/extension
# Run: ant -f build.xml (this builds the 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.
# 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.

Revision as of 18:02, 3 October 2011

Releasing Mozmill has a lot of moving parts. Here's how it's done.

(See https://bugzilla.mozilla.org/show_bug.cgi?id=691368 for the bad page title)

Bump the Version Numbers in the Source

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.

Make a bug and attach the patch for review.

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 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

  1. Once you have a final version, cd into mozmill/mozmill/mozmill/extension
  2. Run: ant -f build.xml (this builds the extension)
  3. 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.
Retrieved from "https://wiki.mozilla.org/index.php?title=Auto-tools/Projects/Mozmill/Release&oldid=354159"