- S2_5 is receiving only occasional commits. 2.5.6 should be released so that it makes it to Debian Stretch before freeze - late this year or in the beginning of January. It's possible that it will be the last release from S2_5.
- S2_6 is stable, and most things getting committed to trunk are not committed there. - We are already piling up things that would make more sense to get committed early in 3.1 cycle than close-to-branching to 3.0. - One conclusion in the earlier freeciv-2.7 speculation was that S3_0 would get branched soon, to cut out need for another version while waiting 3.0. With these points in mind, I'm proposing setting 02-Jan-17 as the S3_0 branching date. That is 24 months after S2_6 branching. The branching date is not a date after which no new features can be started, but rather just an option to have some committed new features targeted to 3.1 (trunk-only). However, I think S3_0 will be a bit different from S2_6 in that latter is about last freeciv-2 release, and as such we've been trying to tie odd ends more than usually. In S3_0 I expect us to be more likely to just postpone things to 3.1, especially if they seem like too distruptive change given where we go in the 3.0 cycle. How does this sound, especially to active developers who have certain features to include to 3.0 in mind? - ML _______________________________________________ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
