As Cocos already started using Pyglet 1.2, and most people with issues are also directed to download the development version, maybe it would be a good idea to release 1.2 officially. Any opinions on what needs to finish before a release can be made?
Rob Op dinsdag 20 januari 2015 03:02:30 UTC+1 schreef Leif Theden: > > Good. Lets get off of google code right away. Personally, I don't care > about pyglet 1.2 as much as I care about making it easy to pull in new > code. A casual look at the sorry list of issues will show many patches > just waiting to be merged, but of course, nobody wants to deal with it > because it is a pain. Not to mention the awful test suite that needs to be > run after merging a diff. Seriously. Why not just move to github or > bitbucket, collect patches, and then worry about 1.2? > > On Friday, December 19, 2014 at 12:35:46 PM UTC-6, Jimmy Newsom wrote: >> >> I noticed that the last update on the site was Submitted by Richard on >> 13-July-2012. I was wondering if this project is over or still being >> actively maintained. >> > -- 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.
