On 17/07/13 00:35, Richard Jones wrote: > [...] > As I said privately, there's no formalised processes with this > project, mostly because there's no project lead. >
OK, after a quick run through the tickets and the repository: - Most tickets refer to pyglet 1.1.x - There are very old tickets - Several tickets have patches (gold!) There are 22 listed committers and, although the pace has been slow after the release of 1.2 alpha1 (1.2 from now on), the project didn't stop until early this year. That's good! I know how difficult is getting things going, so here follows my proposal: It doesn't look like 1.1.x is being maintained, so suggest we keep 1.1.4 as stable but work towards releasing 1.2 alpha2 before checking the roadmap and start striking things out for an eventual 1.2 beta1. To do this, I would go trough the bug list and... - Ask bug reporters to confirm bugs with 1.2 alpha1 (it is going to be very painful with very old tickets, so some tickets will be closed as "deprecated"). - Fix bugs in 1.2 (default branch). - When we get to a dead end with the bug list, release 1.2 alpha2. - Make 1.2 easier to install (put docs online too) and encourage users to try it (for me has been quite stable and joystick support is a big selling point!). Please let me know what you think. Specially I'd love comments from any of the committers. Regards, Juan -- jjm's home: http://www.usebox.net/jjm/ blackshell: http://blackshell.usebox.net/ -- 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 http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/groups/opt_out.
