Hi, I almost missed your mail as my mail program folded it into an ancient thread with the same title. I was actually about to write a similar mail but didn't get to finish it up before I saw yours. :)
Robert Bradshaw wrote: > It seems like there's consensus that we're overdue for another > release totally. > (1) Get the current -devel branch out as 0.11.3 as soon as possible. > Hopefully, this will just require testing lxml Works for me. AFAIR, there were no really major changes since 0.11.2 anyway, mostly fixes. > 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. Let's do that. > (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. I consider it mostly stable, except for the few remaining test case failures. Would be great if you could take a look, Robert. > (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? Early October should work for me, and I think the overall time frame is ok. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
