Branching from discussion in "1.0.6 and 1.1.5 releases" thread: https://groups.google.com/d/msg/trac-dev/1aDVJ79PUHQ/y-adWoNcf0EJ
On Wednesday, April 29, 2015 at 2:49:52 AM UTC-7, cboos wrote: > > > We should think about how we'll support the 1.0.x line after 1.2 is > > released. I'd like to push only critical fixes to 1.0.x after 1.2 is > > released, but please let me know your thoughts. > > > > Yes, once 1.2 is out, there will be no reason to continue adding > features or non-critical fixes to 1.0. We don't even need to label it as > "LTS", I think we could plan to have 1.2 as the next long term stable > basis after 0.12. > > -- Christian > I've created a 1.0.8 milestone (1) with the idea that we'll continue development in the standard pattern until the 1.2 release. After the 1.2 release, we'll be developing towards 0.12.9 / 1.0.9 / 1.2.1 / 1.3.1, with only critical fixes targeted to 0.12.9 / 1.0.9. 0.12.8 / 1.0.8 / 1.2 currently have a due date of 01 September 2015. To achieve this, we'll probably need to have tickets for 1.2 implemented by the beginning of August, and then 1 month for testing, updating translations, updating documentation and minor fixes. I assume a string freeze sometime in early August, and maybe we can finally deal with pulling in the translations from Transifex. - Ryan (1) http://trac.edgewall.org/milestone/1.0.8 -- 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.
