Christian Boos wrote: > What about getting 0.12 released this year, still?
Yes, oh yes, please ;-) > we should now start to think about a > feature freeze and reduce drastically the number of tickets that can > realistically be finished for 0.12. We still have plenty of opened > tickets for 0.12, but as usual we will mercilessly move the non-critical > ones to some later milestone, like 0.12.1 for bugs and 0.13 for > enhancements (*). Also, I've started to add the "needmajor" keyword on > tickets which need some API breakage in order to be completed, meaning > they should be done for 0.12 *or* will have to wait for 0.13 or later. All excellent initiatives. > (*) before that'll happen, maybe move 0.12.1 tickets to 0.12-stable and > 0.13 ones to 0.1x, for minimizing the later moves. Also an excellent idea. Maybe call the next major milestone "trunk" or "next-major", so as to remove all "numbered" references. Actually, what about using more descriptive names all around: 0.12.1 -> 0.12-stable 0.13 -> next-major 1.0 -> idea-pool 2.0 -> alien-tech :-) That should avoid having to explain the meaning of the various milestones repeatedly. Thanks for all your efforts! -- Remy
signature.asc
Description: OpenPGP digital signature
