At the conclusion of each milestone I've been copying the ApiChanges (1) page forward, e.g. HEAD revision of 1.1.3 to create 1.1.4. I'm not sure what was intended originally, but I didn't want to try and piece together a 1.2 page from 1.1.1, 1.1.2, ..., and that would be needed if each 1.1.x ApiChanges page only contained changes for that milestone.
What results is a series of pages with a lot of duplicated content. Peter added the version for each new interface (2). That has me thinking that it might be better to prepare a single page for the next series of development releases, name it 1.3.x and note the milestone in which each item was added, removed or changed. I'm seeking feedback on what the developers think will be easiest to maintain, and what the consumers of the ApiChanges documentation think will be easiest to read. Thanks, - Ryan (1) http://trac.edgewall.org/wiki/TracDev/ApiChanges (2) http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.4#NewInterfaces -- 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 trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
