Hello again, This Friday on #trac (freenode IRC), we were discussing the multirepos merge and more generally the 0.12 schedule. I wanted to remind people of some old ideas I sent to the Trac-dev list, but I couldn't find the reference back then. Now I have it:
http://groups.google.com/group/trac-dev/msg/4207c000d7c8be9c The main idea exposed there, in the second part of the mail, was to create *intermediate releases* during a major development period, once in a while (e.g. every 3 months) or after some new major feature has stabilized. Those "pre" releases can be used as reference points (0.Xpre1, 0.Xpre2, ...), they will help gathering more user and plugin developer feedback, and they can be used to document more precisely the API changes (see a detailed example in the mail linked above). A related idea was that major features could be tracked in topic branches and have their own (sub)milestone, which is what we finally did for multirepos. So I'd like to reopen this discussion, as I think the ideas exposed above are still relevant, but maybe more for 0.13 than for 0.12, which has seen a "traditional" period of > 1 year of development on trunk with no intermediate releases and which is now reaching its conclusion anyway (and the details of it can be discussed in a separate mail - "Tentative 0.12 Release Schedule"). -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
