I understand what you mean about pull requests directly to the default branch, but the 1.2.x branch is nicely separated with each released tagged. It seems to be fairly well organized this way.
On Saturday, April 2, 2016 at 10:12:28 PM UTC+9, Daniel Gillet wrote: > > Hi Benjamin, > > Thanks for your help. I did also some researches on my side. It's good to > know that pyglet is expecting named branches. I think I'll manage to do > that. I'm just a bit surprised that I should propose that pull request onto > the default branch. The reason being that I can see some work that is meant > to be part of a 1.3 release. But my pull request is not really meant to be > for that release. Or maybe it has to. Anyway, I'll just make a named branch > from the pyglet tip and see how it goes. :) > > Daniel. > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
