canmove, Confirmed users
1,635
edits
Releases/Code Names: Difference between revisions
→How
(Created page with "We are using code names to refer to branch code releases while they are in development. == Why == This is the scenario we want to avoid: * We are working on Firefox 4.0.5. It ...") |
(→How) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
We are using code names to refer to branch | We are using code names to refer to '''branch point releases''' while they are in development. | ||
== Why == | == Why == | ||
| Line 23: | Line 22: | ||
For example, the Firefox 4 update codenames relate to the rainforest and go as such: | For example, the Firefox 4 update codenames relate to the rainforest and go as such: | ||
* '''Anteater''' - this was a name reserved for a quick-turnaround update if problems were found with Firefox 4 | * '''Anteater''' - this was a name reserved for a quick-turnaround update if problems were found with Firefox 4 | ||
* '''[[Releases/Firefox 4/Macaw | Macaw]]''' - this was the first regularly scheduled point release for Firefox 4 | * '''[[Releases/Firefox 4/Macaw | Macaw]]''' - this was the first regularly scheduled point release for Firefox 4 | ||
While working on Macaw, if a bad security issue comes up we would create an update with a name relating to the rainforest starting with B up to M. Because the name '''Macaw''' is independent of the version it will eventually ship as all the issues above are mitigated. | While working on Macaw, if a bad security issue comes up we would create an update with a name relating to the rainforest starting with B up to M. Because the name '''Macaw''' is independent of the version it will eventually ship as all the issues above are mitigated. | ||