Release Trac 1.0.3 / 1.1.3

[Ryan J Ollos]

This task ticket is used to coordinate the finalization and testing of the next stable versions of Trac, 0.12.7 and 1.0.3, and the next developer stable version of Trac, 1.1.3.

It's still early in the development cycle, but I want to highlight some proposed dates and document some changes that are intended to make the release process easier. Some proposed dates:

• Dec 26th: Stop development on stable branches and trunk and start the testing and release cycle.
• Jan 2nd: Release Trac 0.12.7 / 1.0.3 / 1.1.3
• TODO Announce string freeze on 0.12-stable and ask translators to update the translations by Dec 20th.

Previous release ticket #11694 has some possible action items.

[Ryan J Ollos]

Discussion about ending development of the 0.12 release line in ​trac-dev/35sr8nwDX64/7uV67b6vN3wJ.

[Ryan J Ollos]

There were many wiki edits associated with #11824 that will need to be applied to the pages under 1.1. I'm not entirely sure what has been done in the past, but there are some hints: TracProject/DefaultWikiPages

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.

Has this porting been done manually in the past, or by merging in the repository? If by merging in the reporting, then once those changes get pulled into 1.0-stable, it sounds like we can merge them into the trunk. The t.e.o wiki could then be updated from the merged changes in the trunk?: TracProject/DefaultWikiPages#sync

Note that porting changes from 0.12 to 1.0 happens quite naturally when we port over the changes from branches/0.12-stable​ to trunk​, but this happens only in the repository, the toplevel pages on t.e.o won't contain these changes. It might be useful from time to time to do a sync the other way round.

[Ryan J Ollos]

I was thinking about moving TracWorkflow#Environmentscreatedwith0.11 to TracUpgrade#UpgradingfromTrac0.10toTrac0.11 and just leaving a one-sentence statement about where to find more info if upgrading from Trac 0.10. The heading Environments created with 0.11 would be changed to Default Workflow. It would be good to reduce the length of the page and move information that is irrelevant to most users from the top of the page. Any thoughts on the change?

[Ryan J Ollos]

Replying to rjollos:

I was thinking about moving TracWorkflow#Environmentscreatedwith0.11 to TracUpgrade#UpgradingfromTrac0.10toTrac0.11 and just leaving a one-sentence statement about where to find more info if upgrading from Trac 0.10. The heading Environments created with 0.11 would be changed to Default Workflow. It would be good to reduce the length of the page and move information that is irrelevant to most users from the top of the page. Any thoughts on the change?

Changes made in 1.1/TracWorkflow@3 and TracUpgrade@106.

[Ryan J Ollos]

Since 0.12-stable is being closed to maintenance I retargeted the new tickets in milestone:next-minor-0.12.x to milestone:next-stable-1.0.x. We can move back any ticket that needs to be fixed on branches/0.12-stable​.

[Ryan J Ollos]

Documentation synced in [13650], merged to trunk in [13651].

[Ryan J Ollos]

wiki:1.1/WikiProcessors@3 should be reverted because the changes merged from the 1.0 documentation in that edit are applicable to 1.1. WikiProcessors@66 reverted some edits that were applicable to the trunk, but not 1.0-stable.

[Ryan J Ollos]

wiki:1.1/WikiProcessors@3 removed and new wiki:1.1/WikiProcessors@3 created that uncommented the example. I had forgotten about the example.

[Ryan J Ollos]

Ticket retargeted after milestone closed