Hello, It's been a very looong time since my last report!
I'm still doing work on pyglet, mainly letting some patches in (from Claudio, Eric, Risimi, Techno, Anatoly, Txema and others) and keeping the bug tracker attended. It will be soon a year since I started contributing to pyglet towards making 1.2 the new stable. It's harder than I thought, but we're in the right direction. I'm going to start tagging issues as "1.2 release blocker", meaning that when I get them closed, I think there should be a 1.2 release as the new stable version of pyglet. You can see current list of blockers: https://code.google.com/p/pyglet/issues/list?q=label:1.2-release-blocker When I have some time I'll try to go through the source code trying to identify things that should be fixed or improved and I'll add them as small bug reports. Anything that didn't pop out in the last 2 years as a bug report is probably not a blocker; but still I want to be sure there's nothing really broken. As always, any help is very welcome! Also Nathan will try to release an new version of AVBin (I've been successfully using 11 alpha 4 for almost a year), and we're trying to get Debian folks to update AVBin packages to a newer version. Exciting times ahead :) After 1.2 is out, perhaps we can plan pyglet's long term future (maintenance, finish things, migrate to github, etc). Obviously I'm not going to be here forever, so pyglet will be whatever YOU want. 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/d/optout.
