On May 1, 8:03 pm, Ben Smith <[email protected]> wrote: > I think we need to agree to a plan for release that we can focus > on.http://code.google.com/p/pyglet/wiki/ReleaseSchedulelooks pretty good > and maybe we should go with it, though I'm afraid I'm not an expert in > some of the areas. We may want to add or remove some things from that > list, as well, to open it more for discussion. I also haven't put as > much time into pyglet as I intended after the 1.1.4 release, but I can > spend a few hours a week working toward getting a release out.
If you were able to coordinate the new release, I'd be willing to provide help in any way that I can. I haven't dug into the 1.1.4 code very much and don't fully understand all the differences between it and 1.2. And I have very little experience working with any of the platforms aside from OS X. It seems like the first big decision to make is whether the next release will be 1.1.5 (based on the 1.1.4 code) or 1.2 based on the trunk. The features that I think are important for the next release, whatever it is called, are: 1. Addition of the input module for joystick support. 2. Python 3 support. 3. Integration of the cocoa code for continued OS X support in the future. 4. Bugfixes since 1.1.4 And not quite as important to me: 5. Screen resolution switching. It probably wouldn't be too hard to backport the joystick stuff and the python 3 support, but trying backport everything else useful that's in 1.2 seems like it would involve quite a lot of work. So I think I am leaning towards just working on a 1.2 release. Are there are any showstopping problems in 1.2 currently? One thing that I have noticed is that the reported frame rates do not appear to be correct (or at any rate, they don't agree with 1.1.4) and I haven't figured out what's going on there yet. The other thing I can think of is that it needs a lot of documentation work. I agree that maybe we should not worry too much at first about getting it working on every possible combination of OS/graphics card/driver and just try to get something out that people can use and report bugs on. If there's anything in 1.2 that's too incomplete let's just strip it out for now. The release schedule on the wiki looks like a good starting point, but I think we should remove as much from that list as we can get away with. So here are some questions for everyone else: 1. What are the features that we absolutely need in the next release? 2. Are you having any major problems in using 1.2? -- 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.
