On 26.03.2015 20:56, RjOllos wrote:
I thought about it some more. We could:
* Have an ApiChanges/1.1 page with annotations showing the 1.1.x
release in which a change was made.
* Remove the 1.1.x annotations when preparing ApiChanges/1.2.
The result is two pages with distinct information. ApiChanges/1.1 page
is easy to create because it can be edited incrementally as tickets
are closed out. ApiChanges/1.2 is easy to create because the only
necessary steps are copying 1.1 and deleting some content. That can
easily be done just prior to the 1.2 release.
I created ApiChanges/1.1, merging ApiChanges/1.1.1 to 1.1.5 and adding
version annotations.
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1
We could delete these pages now:
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.1
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.2
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.3
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.4
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.5
Or maybe better just replace them with a redirection link to 1.1.
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
