Changes between Version 35 and Version 36 of TracProject/DefaultWikiPages

Timestamp:

Aug 8, 2011, 11:08:34 AM (13 years ago)

Author:

Christian Boos

Comment:

better document the life-cycle of the default page, starting by re-arranging the information already present

TracProject/DefaultWikiPages

@@ -1 +1 @@
 = Wiki pages to be included in a release =
+[[PageOutline(2-3)]]
+== Review 
+This page is used to keep track of the informal review process of the default pages, which happens every once in a while, usually shortly before a new major release.
 
+=== Page list
 ''This list only provided for convenience. See [source:/trunk/contrib/checkwiki.py#latest checkwiki.py] for the official list of wiki pages to be included in releases.''
-
 
 The following table lists the pages that will be included in the next [milestone:0.13] release, and the name of the person who proof-read and possibly updated/corrected that page.
@@ -64 +67 @@
 
 === Status ===
-Currently preparing the 0.11 release
+Next review will be for the [milestone:0.13] release (still under development).
+
+
+== Life-cycle of the default wiki pages
+=== When migrating to a new major release
+
+ - Prepare documentation below !wiki:0.X/<page> by copying current TracGuide pages wiki:<page>
+ - When the beta testing period begins:
+    - rename the default pages to !wiki:0.X-1/<page>, taking care of replacing dynamic content in TracAdmin, TracIni, TracSyntaxColoring (starting with 0.12) and WikiMacros by the output generated by Trac 0.X-1
+    - rename the !wiki:0.X/<page> pages to wiki:<page>
 
 
 === How to maintain the default wiki pages in sync? === #sync
-
+ ''the following section corresponds to the 0.11 / 0.12 period; need to be updated to take advantage of the Mercurial mirrors''
 As some content is only pertinent on t.e.o and not in the packaged docs, downloading new content from t.e.o will lead to repeated merge, so we need a system that can handle them efficiently.
 
@@ -143 +155 @@
 Note also that this method is scalable, and that it can easily be used for tracking ''several'' sources. For [milestone:0.12], we could track the toplevel changes ("wiki-guide" branch in the above), as well as the 0.12 specific pages (0.12/..., in another "wiki-0.12-guide" branch).
 
-
-== TracGuide pages on t.e.o
-
-=== When migrating to a new major release
-
- - Prepare documentation below !wiki:0.X/<page> by copying current TracGuide pages wiki:<page>
- - When the beta testing period begins:
-    - rename the default pages to !wiki:0.X-1/<page>, taking care of replacing dynamic content in TracAdmin, TracIni, TracSyntaxColoring (starting with 0.12) and WikiMacros by the output generated by Trac 0.X-1
-    - rename the !wiki:0.X/<page> pages to wiki:<page>
-