12 # See the License for the specific language governing permissions and |
12 # See the License for the specific language governing permissions and |
13 # limitations under the License. |
13 # limitations under the License. |
14 |
14 |
15 """Release tag string for display in templates (and possibly other uses). |
15 """Release tag string for display in templates (and possibly other uses). |
16 |
16 |
17 Set RELEASE_TAG to a release string, commit that change as the *only* change |
17 Steps (currently done by hand, but too be scripted in the future) to make |
18 in the commit, and then use 'svn copy' on the revision produced by committing |
18 a release: |
19 the updated RELEASE_TAG to create a tags/ release directory of the same name |
|
20 as the string value. |
|
21 |
19 |
22 After creating the tag, set RELEASE_TAG to None until the next release. |
20 1) set RELEASE_TAG in this file to a "release candidate" release string that |
|
21 ends in "rc" |
|
22 |
|
23 2) commit this file *by itself* in its own commit |
|
24 |
|
25 3) use 'svn cp' to create a release branch in /branches/ with exactly the |
|
26 same name as the contents of the RELEASE_TAG string |
|
27 |
|
28 4) set RELEASE_TAG back to None in /trunk/ |
|
29 |
|
30 |
|
31 To finalize a release candidate in a release branch for a push to the live |
|
32 web site: |
|
33 |
|
34 1) in the release branch, change RELEASE_TAG to remove the trailing "rc" |
|
35 |
|
36 2) commit this file in the release branch *by itself* in its own commit |
|
37 |
|
38 3) use 'svn cp' to create a tag in /tags/ with exactly the same name as the |
|
39 contents of the RELEASE_TAG string |
|
40 |
|
41 4) put the release branch in a state where it is ready for additional patches |
|
42 after the tag by setting the end of the RELEASE_TAG string to "p0" |
|
43 |
|
44 |
|
45 To re-release a previously-tagged release branch after a patch for a push to |
|
46 the live web site: |
|
47 |
|
48 1) increment the "patch suffix" of the RELEASE_TAG string to the next integer |
|
49 (for example, "p0" becomes "p1", so the first tagged patch release will |
|
50 always be "p1", not "p0", which is just a placeholder) |
|
51 |
|
52 2) (same as #2 for a release candidate) |
|
53 |
|
54 3) (same as #3 for a release candidate) |
|
55 |
|
56 4) (there is no step 4) |
23 """ |
57 """ |
24 |
58 |
25 __authors__ = [ |
59 __authors__ = [ |
26 '"Todd Larsen" <tlarsen@google.com>', |
60 '"Todd Larsen" <tlarsen@google.com>', |
27 ] |
61 ] |
28 |
62 |
29 # previous RELEASE_TAG = '0.0a20081123' |
|
30 |
63 |
31 RELEASE_TAG = None |
64 RELEASE_TAG = '0.0a20081123rc' |
32 |
65 |