Remy Blank wrote: > [email protected] wrote: > >> i was wondering if the trac project could do time based releases? e.g. >> release a version every 3 months, or 6 months, no matter how many >> ticktes got fixed. >> > > This would probably be quite easy for bugfix releases (0.11.2, 0.11.3, > ...), and more difficult for feature releases (0.12, 0.13, ...), as > trunk is not always in a stable state (it usually is, though). > > But I suppose that if we switch to time-based releases, we would have to > change the development model anyway, along the lines of: > > - 0.x are time-based releases > - 0.x.y are security releases, i.e. only happen if security issues are > fixed > - 0.x is only supported until 0.(x+1) is released > > I suppose that this model could be more difficult for plugin authors, as > they would have to track trunk development more closely. > > FWIW, I'd be +1 on the idea, provided we find a suitable development / > support model. >
Well, we already had a time based release in place for the coming milestones, only we didn't stick to it :-) I hope I'll be able to close some of my 0.11.3 issues in the coming days and then we can test and release soon after (say, mid-February). I just created 0.11.4 which now contains the tickets that used to be targeted at 0.11.3 tickets. If you feel some of the tickets there should really be fixed in time for 0.11.3, then please move them back. We can indeed try to stick with more regular 0.11.x releases after that. -- 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 -~----------~----~----~----~------~----~------~--~---
