On Sun, Aug 16, 2009 at 11:20 AM, Martin O'Leary <[email protected]>wrote:
> > Pure bugfix releases of libraries have been allowed (welcomed!) in > previous Pyweeks after the library deadline. I don't think anyone > would have any problems with a Pyglet 1.1.4 release being used, > assuming such a release happens before Pyweek itself. That's good news. > > > * It would be possible to have a "stable 1.1.4 release" and an "unstable > > 1.2.0 release" at ...almost the same time.... > > I think the model used previously of successive alpha and beta > releases worked very well. We could have 1.2alpha1, 1.2alpha2, etc, > until we're sure that the API is fixed, then 1.2beta1, 1.2beta2, etc, > until it's (relatively) bug-free, then a full 1.2 release. This could > easily sit beside 1.1.4, and indeed 1.1.5 if such a thing turns out to > be necessary. Hopefully by then 1.2 should be stable enough that the > 1.1 branch can be left behind. That all makes sense to me. > A change in version control systems could take place at any point in > the above, really, if it's decided that one is necessary. Obviously it > would be helpful if there was a consensus among developers about what > was happening, but that sits hand-in-hand with what I've said > previously about decision-making structures. The important thing in my > view is clarity about what decisions have been made, and unity in > implementing decisions once they have been. For non-irreversible decisions, letting an apparent consensus arise, and then saying something like "ok, i'll assume we'll do X unless anyone objects in the near future (e.g. 2 days)", seems best to me (given a willingness to reconsider, and toleration for individual differences); for irreversible decisions, we can hope that this same sort of process can work if there is no controversy (though it would go through more stages of certainty and take longer), and if that fails we can deal with it at the time, e.g. by begging Alex to weigh in. I think it will become clear who's doing the work and/or keeping good track of things, and that this will be mostly a handful of people, so it's not too much of a burden to wait and see what all those people think before being reasonably certain that "a decision has been made". When there is consensus (either on a decision, or on a set of issues and the need for a decision), it might also be useful to make a wiki page summarizing it (and to have one page for the near-future roadmap in general), though the actual discussion probably still works best within this group. (All IMHO.) - Bruce --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" 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/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
