Software Update:Nightly update infrastructure: Difference between revisions

Software Update:Nightly update infrastructure (view source)

Revision as of 09:42, 2 October 2007

121 bytes added , 2 October 2007

→‎AUS itself: - bring up to date

NThomas

Confirmed users

4,293

edits

@@ Line 146: / Line 146: @@
 ==AUS itself==
-To provide this content, AUS maps the client version (%VERSION%) from the request to $update_version of snippet store. This was the mapping on May 15 2006:
+To provide this content, AUS maps the client version (%VERSION%) from the request to $update_version of snippet store. This was the mapping on Oct 02 2007, which uses wildcard matches since [https://bugzilla.mozilla.org/show_bug.cgi?id=364628 bug 364628]:
- '1.0+', '1.4', '1.4.1', '1.5' => '1.5',
+    'Firefox'     =>  array(
- '1.5.0.1' => '1.5.0.1',
+        '1.5.0.*' =>  '1.5.0.x',
- '1.5.0.2' => '1.5.0.2',
+        '2.0*'    =>  '2.0',
- '1.5.0.3' => '1.5.0.3',
+        '3.0a*'   =>  'trunk'
-  '1.5.0.4' => '1.5.0.4',
+    ),
- '2.0', '2.0a1', '2.0a2', '2.0a3', '2.0b1', '2.0b2' => '2.0',
+    'Thunderbird' =>  array(
- '1.6a1', '3.0a1' => 'trunk'
+        '1.5.0.*' =>  '1.5.0.x',
-(This is a more compact form of the [http://lxr.mozilla.org/mozilla/source/webtools/aus/xml/inc/config-dist.php actual definition], each mapping should be on it's own line)
+        '2.0*'    =>  '2.0',
+        '3.0a*'   =>  'trunk'
+    ),
+    'Sunbird'     =>  array(
+        '0.7*'    =>  'branch',
+        '0.6a1'   =>  'trunk'
+    )
+This is an abbreviated version with only the versions still in use (except Firefox 1.5.0.x, which is beyond end-of-life), the current config is [http://lxr.mozilla.org/mozilla/source/webtools/aus/xml/inc/config-dist.php#83 here].
-So there is a many to one relationship between application versions from a code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement of v2.0 and will have versions 2.0a1, a2, a3, 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 application versions from a code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for development of v2.0 and will have versions 2.0a1, a2, a3, b1,b2, RC1, 2.0 final and then the 2.0.0.x security releases.