947
edits
Auto-tools/Projects/Mozmill/Release: Difference between revisions
Auto-tools/Projects/Mozmill/Release (view source)
Revision as of 18:02, 3 October 2011
, 3 October 2011overall fixes
(→Releasing a Preview Release (aka Release to PyPi): correct title) |
(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 == | ||
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 | |||
= 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. | ||