Changes between Version 41 and Version 42 of TracProject/DefaultWikiPages

Timestamp:

Nov 19, 2014, 9:02:19 AM (9 years ago)

Author:

Ryan J Ollos

Comment:

Notices are no longer contained in wiki content after #11725.

TracProject/DefaultWikiPages

@@ -88 +88 @@
 The TracGuide pages for [[0.12/]] are not likely to change much, but just in case...
 
-Their content is usually matching the one which has been shipped in the corresponding release, except for:
- - a banner mentioning the current version and linking to the page corresponding to the //previous// release (e.g. for TracWiki: **Note: this page documents the 0.12 version of Trac, see [[0.11/TracWiki]] if you need the previous version**)
- - the edits users have made in the meantime, which will be reviewed and integrated in the next minor releases 0.12.x.
+Their content is usually matching the one which has been shipped in the corresponding release, except for the edits users have made in the meantime, which will be reviewed and integrated in the next minor releases 0.12.x.
 
 === How to maintain the 0.12 wiki pages in sync? === #sync012
@@ -101 +99 @@
 $ python ../../../contrib/checkwiki.py -d -C -p 0.12
    }}}
- - repos:cboos.hg:trac-guide-0.12 is the integration branch for the changes from t.e.o; changes that should not been merged in are discarded (once), like the version specific banner, the static content replacing macro expansions, etc.
+ - repos:cboos.hg:trac-guide-0.12 is the integration branch for the changes from t.e.o; changes that should not been merged in are discarded (once), like the version specific banner (removed after [milestone:0.12.6]), the static content replacing macro expansions, etc.
 
 Once the initial setup is done, all what is needed is usually:
@@ -117 +115 @@
 The changes that occurred in a toplevel page since the corresponding `X/` page has been created are eventually ported, if those changes are also relevant for the new major version.
 
-Then the `X/` pages are copied to toplevel, with the appropriate change in the warning banner.
-
-All toplevel pages are reviewed and updated as needed for the new version `X`.
+Then the `X/` pages are copied to toplevel. All toplevel pages are reviewed and updated as needed for the new version `X`.
 
 The `X/` pages won't be touched anymore until we'll prepare the migration to the `(X+1)/` release and make a "backup" of the default pages below `X/` (thereby overwriting the old dev pages).
@@ -138 +134 @@
 $ python ../../../contrib/checkwiki.py -d -C
    }}}
- - repos:cboos.hg:trac-guide-1.0 is the integration branch for the changes from t.e.o; changes that should not been merged in are discarded (once), like the version specific banner, the editing caveats, etc.
+ - repos:cboos.hg:trac-guide-1.0 is the integration branch for the changes from t.e.o; changes that should not been merged in are discarded (once), like the editing caveats, etc.
 
 Once the initial setup is done, all what is needed is usually: