I agree with the other opinions expressed about not replacing SVN or expanding pyglet's scope for the time being. There is enough to do just with fixing open issues and revising the way in which decisions about pyglet are made.
It seems to me that the most difficult immediate issue for the future of pyglet is what to do about the divergence between the 1.1-maintenance branch (off of which all releases have been made) vs. the trunk (sometimes called the 1.2dev branch). The incompatibility between them can confuse new users and new developers, and leads to more work and possible confusion for all maintainers. Examples of the confusion: what to check out, which branch(es) to fix bugs in, and what to do with code in the experimental subdirectory which only works with the maintenance branch. It would be great if someone who knows could summarize: - the goals and specific elements of the refactoring represented by the trunk; - its status, relative to those goals; - advice about how to handle this going forward. I don't know if anyone but Alex understands this fully, but I know at least some other developers know much more about how these branches differ than I do. I think the near-term highest priority in the code, besides fixing individual bugs, is getting it back to a state of having only one important branch -- that is, either abandoning the trunk (reverting to the 1.1-maintenance branch) or finishing the trunk and abandoning further development in the 1.1-maintenance branch. - Bruce Smith --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
