On Sun, Aug 16, 2009 at 2:24 PM, Ben Smith <[email protected]>wrote:
> > Well, the main reason I did it this way is because I didn't feel that > there was firm consensus as to what should be done. I don't mind > doing this work on the maintenance branch instead, I just didn't want > to go committing to an 'official' branch without other people weighing > in - yet I wanted to *do* something. > > I agree with you, the more branches the same work is done in, the more > complicated things get. My social concern is the only motivation for > this branch. I'd like to merge it in as soon as possible, if it's not > going to cause problems. Matter of fact, while others are working on > still open issues in the 1.1-maint branch I can go over these closed > in 1.2 issues without much problem. > > So, if people want these changes on the 1.1-maintenance branch, I'll > put them in. I'd like to wait a day or two to hear from interested > parties before I do any committing on an 'official' branch. > > -b My view is that it's better to commit directly to 1.1-maintenance -- this reduces potential confusion, reduces potential eventual merge conflicts, and requires less coordination. (And if you make a mistake, you or someone else can always revert it -- it's not a big deal.) But, as only one of the interested parties, I am totally sympathetic with your waiting for an "ok" from the others. But I would point out that other committers are already committing directly to 1.1-maintenance (I think), and I also plan to do that if I have time to do any commits. - 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 -~----------~----~----~----~------~----~------~--~---
