Confirmed users
4,293
edits
mNo edit summary |
m (bug 337910 added mapping for 2.0a3) |
||
Line 124: | Line 124: | ||
'1.5.0.3' => '1.5.0.3', | '1.5.0.3' => '1.5.0.3', | ||
'1.5.0.4' => '1.5.0.4', | '1.5.0.4' => '1.5.0.4', | ||
'2.0', '2.0a1', '2.0a2', '2.0b1', '2.0b2' => '2.0', | '2.0', '2.0a1', '2.0a2', '2.0a3', '2.0b1', '2.0b2' => '2.0', | ||
'1.6a1', '3.0a1' => 'trunk' | '1.6a1', '3.0a1' => 'trunk' | ||
(This is a more compact form of the actual definition, each mapping should be on it's own line) | (This is a more compact form of the actual definition, each mapping should be on it's own line) | ||
So there is a many to one relationship between versions from a particular code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement of v2 and will have versions 2.0a1, a2, b1,b2, RC1, ... and finally 2.0. The situation with the Mozilla1.8.0 branch needs fixing up (partly [https://bugzilla.mozilla.org/show_bug.cgi?id=328497 Bug 328497]), an $update_version of "1.5.x.y" would be flexible. | So there is a many to one relationship between versions from a particular code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement of v2 and will have versions 2.0a1, a2, b1,b2, RC1, ... and finally 2.0. The situation with the Mozilla1.8.0 branch needs fixing up (partly [https://bugzilla.mozilla.org/show_bug.cgi?id=328497 Bug 328497]), an $update_version of "1.5.x.y" would be flexible. |