I would support moving to mercurial, since Google code now supports it and especially if it eases patch integration, which it seems like it should. Should also make branch management easier, which was something I never liked much in svn.
As for 1.2 I think we should come up the minimum amount of work necessary to get out a first alpha. I propose that anything Alex was not confident in should be omitted from a first alpha to get it out more quickly. There's probably a bunch of work in just testing and verifying things. And I'm unsure what the state of the documentation is. I'm currently working on a game engine project that builds on top of pyglet (and is intended to support pygame one day as well, but not yet), so I have a vested interest in seeing development continue, especially the OSX cocoa support. I also have access to machines running 10.4, 10.5 and 10.6 so at a minimum I can help test. I'd be interested in helping see it through, though I'm not well versed in the Cocoa apis. I don't want to over-promise, but I can lend some cycles. Tristam, if you could post a little summary on what works, is considered done and what needs attention, I can see if there is anything I can help with. -Casey On Sun, Jan 24, 2010 at 11:35 AM, Ben Smith <[email protected]> wrote: > Hello all, > > If there are critical issues in the 1.1.4 branch, we can look at > fixing them in a 1.1.5 release. > > Better, though, to move to 1.2 if the maintenance branch is working > well enough. Alex Holkner put together a summary of feature changes > here: http://groups.google.com/group/pyglet-users/msg/9733fab4436e635d > and the entire thread at > http://groups.google.com/group/pyglet-users/browse_thread/thread/700c63844ece86c2/e5b22b9d0c6320c4 > is worth going over. > > There are some other things that have occurred in the interim. > Unrelaible timing on Windows, and issues with 64-bit OSX 10.6, off the > top of my head. I feel that finding a way to make the testing system > more automatic would be nice, too, though there are very likely some > situations where tests must be inspected visually. I'd like to see > these things in 1.2, but that's just an opinion and I'm afraid I > haven't kept up with the developments on the OSX things. > > Also, to open up a fun can of worms - now seems like a good time to > move to a dvcs, particularly Mercurial since google code supports it. > Are there compelling reasons to stick with SVN? I'd used git before > this discussion came up in August, and have been working with both git > and Mercurial since. A lot of the issue ports and backports would > have been easier with one of these, due to the overhead in tracking > down historical diffs to find out which things changed and when. I > would personally prefer working with hg over SVN. > > Thanks, > -b > > -- > 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. > > -- 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.
