TracEnvironment not updated for 0.11

[jpwasp@…]

The page TracEnvironment does not appear to be updated for 0.11 in the release; or, the page is not written generically. I know this is wiki and I can change it but as I'm trying to use the page to learn the differences between 0.10 and 0.11 I'm unsure to modify it. Here are the items I think are in question:

• templates - Custom environment-specific templates.
  • site_css.cs - Custom CSS rules.
  • site_footer.cs - Custom page footer.
  • site_header.cs - Custom page header.
• wiki-macros - Environment-specific Wiki macros.

These have references to ClearSilver and macros. I think macros aren't supported in 0.11 anymore.

As a side note, it would be useful to mention the directories you need to delete when upgrading to Trac 0.11. Right now I had to figure out how to manually upgrade removed features (such as css styles).

[jpwasp@…]

OK after some research I feel more confident about updating the documentation, so I updated TracUpgrade, TracEnvironment, and TracWiki.

I found other bugs, too. The VERSION file is Trac Environment Version 1 in 0.10 and 0.11 even though the directory structures are somewhat incompatible (logically not technically). And, the wiki update doesn't remove 0.10 pages that were removed. I'll search for these bugs and file them later.

[Christian Boos]

Updates synced in r6980, thanks!

[Jason Winnebeck <jpwasp@…>]

Awesome; I've found other problems with other wiki pages. What is the process for highlighting that changes like the ones made for this ticket should make it into release? Or do I just make the change and the developers are watching the timeline?

For example, on TracWikiMacros there are "source" links, which won't work in the host environment.

[Jason Winnebeck <jpwasp@…>]

Uh, the last comment wasn't a sarcastic "awesome" the awesome referred to r6980, not the problems in TracWikiMacros :)

[Christian Boos]

I periodically review and merge Wiki changes made to TracGuide pages on t.e.o. (using the source:trunk/contrib/checkwiki.py​ to download them locally). So don't hesitate to fix problems as you see them, directly in those Wiki pages.

The only exception being the TracIni page, where updates to configuration settings documentation should be mentioned in a Notes section (or even better, sent as patches against the source code where that documentation lives).