Robert Bradshaw wrote: > It seems like there's consensus that we're overdue for another > release, so I propose that we try to get a release out in the next > couple of weeks. Before I loose all you non-coders, if anyone sees > something that they really want to see in the next release, please > stick/move the ticket to 0.11.3 or 0.12 (no promises, but it could > help establish priority). > > How about > > (1) Get the current -devel branch out as 0.11.3 as soon as possible. > Hopefully, this will just require testing lxml, sage, and throwing > out a couple of release candidates. I've assigned out some tickets at > > http://trac.cython.org/cython_trac/query? > status=assigned&status=new&status=reopened&group=milestone > > in the next week, lets all at least look at them, and resolve them if > they're quick or bump them if they're not. I'll look at the long- > overdue integer conversion review. > > (2) Let's try to get -unstable out for 0.12. I actually don't even > know how "unstable" it is, but I think it's not far off from being > ready. > > (3) Also in preparation for 0.12, let's go over all the tickets and > see which, if any, are low-hanging fruit. > > I also propose before 0.12 hits, we do a cython bug day. This is > something we've done with Sage and it works well for getting a lot > done in a little amount of time, especially those pesky little ones > that no one ever looks at. Essentially, all of us get together on IRC > and try to snuff out as many bugs as possible in a 24 hour period. > Maybe end of September/early October, with 0.12 coming out mid/late > October?
I think this sounds fine. I'm not too sure about the bug day but I'd like to, I'll have to see when 0.12 approaches if I feel I've had an efficient week and can slack a day... :-) -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
