637
edits
BMO/new-version: Difference between revisions
no edit summary
DaveLawrence (talk | contribs) |
DaveLawrence (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{note|These activities should be completed before or at the same time we have the merge for the next major release of Firefox.}} | {{note|These activities should be completed before or at the same time we have the merge for the next major release of Firefox.}} | ||
= Using Docker to quickly add versions and milestones without the UI = | |||
== Setup == | |||
* You will need to be in the <code>editcomponents</code> permissions group for this to work. | |||
* Install Docker support for your operating system https://www.docker.com/get-started | |||
* You will need to clone the '''saneutils''' Github repository as you will need to configure the config.json file to edit milestones and versions. | |||
** <code>git clone https://github.com/mozilla-bteam/saneutils saneutils; cd saneutils</code> | |||
** <code>cp config.json.example config.json</code> | |||
** You will need to look at your current browser cookies for the bugzilla.mozilla.org site and find the Bugzilla_login and Bugzilla_logincookie values. There are cookie manager extensions that make this simpler. | |||
** Edit the config.json file and place those values in the bugzilla.mozilla.org section for the respective keys. | |||
== Milestones == | |||
Example: Below is the command for editing the '''Firefox''' milestones. | |||
<code> | |||
docker run --rm -ti -v "$(pwd)/config.json:/app/config.json" mozillabteam/saneutils ./edit-milestones.pl --urlbase https://bugzilla.mozilla.org --product Firefox | |||
</code> | |||
This will pull the <code>mozillabteam/saneutils</code> Docker image locally and then spawn vim with a list of all milestones for '''Firefox''' loaded. | |||
The format for the milestones is: | |||
<code> | |||
id:0000 100 Milestone 10 [x] | |||
</code> | |||
Where <code>id:0000</code> is an identifier used to track changes to the milestone (such as renames), | |||
<code>100</code> is the sort key (used for sorting the milestones in the UI) and <code>Milestone 10</code> is the milestone name. | |||
The portion inside square braces (<code>[]</code>) is the active status. It can be either <code>[x]</code> for enabled or <code>[_]</code> for disabled. | |||
The workflow here involves making changes using the text editor, saving the file, | |||
and exiting. Any changes made to the file will be applied to the system passed to <code>--urlbase</code>, | |||
so if a mistake is made simply quit the editor without saving. | |||
Changes made to the sort key, name, and active checkbox will cause updates to the milestone. | |||
Renames of milestones with no bugs are simple renames; renames of milestones *with* bugs will cause | |||
bug updates to happen, so it is advisable to do this with a Bugzilla account that is a *silent user*. | |||
Adding new milestones is done by adding new lines without the <code>id:XXXX</code> prefix, such as: | |||
<code> | |||
2710 Firefox 71 [x] | |||
</code> | |||
Note all three elements (sortkey, name, active checkbox) are required. | |||
Finally, deleting lines will cause those milestones to be deleted -- but you cannot delete milestones that have bugs associated. | |||
Repeat the above Docker command for each product, replacing '''Firefox''' with the next product name. Remember to use quotes for product names with spaces in it. | |||
== Versions == | |||
Updating versions is very similar to the above Docker command. Instead of using <code>./edit-milestones.pl</code>, change it to <code>./edit-versions.pl</code> before executing. | |||
The text that will be edited it also very similar except there is no value for sortkey so that column is omitted. | |||
= Adding a new "rapid release" version to Firefox/Core/Thunderbird = | = Adding a new "rapid release" version to Firefox/Core/Thunderbird = | ||
| Line 15: | Line 73: | ||
Only members of the <code>mozilla-next-drivers</code> group may set a tracking flag to something other than ''?''. Members of the <code>canconfirm</code> group can set status flags or set a tracking flag to ''?''. | Only members of the <code>mozilla-next-drivers</code> group may set a tracking flag to something other than ''?''. Members of the <code>canconfirm</code> group can set status flags or set a tracking flag to ''?''. | ||
* copy cf_tracking_thunderbird''N'' to cf_tracking_thunderbird''N+1'' | |||
* copy cf_status_thunderbird''N'' to cf_status_thunderbird''N_1'' | |||
* edit the flags for previous (now released) versions (N-3) and uncheck 'active': | * edit the flags for previous (now released) versions (N-3) and uncheck 'active': | ||
** cf_tracking_firefox''N-3'' | ** cf_tracking_firefox''N-3'' | ||