Christian Boos wrote: > Now for the next steps, I think the tasks already mentioned above > (#7715, #7687, the other smaller tickets with a patch) can be finalized > this week.
Ok from my side for #7715, I'm almost done with the 0.11-stable backport. > Then an upgrade of t.e.o could be done this week-end and a > "freeze" and testing period of one week could follow, as we did with > quite some success with 0.11.4(rc1,rc2), to avoid the usual Python 2.3 > breakage ;-) Sounds good. How about tracking the release testing in a ticket, as I suggested in ReleaseTesting[1]? As soon as rc1 is ready, we can put all the people on that page in CC, and they can report back when they are done. I'll clean up the page tomorrow. [1] http://trac.edgewall.org/wiki/TracDev/ReleaseTesting > We could therefore > move the current 0.11.6 tickets to 0.12.1, as the plate is already full > for 0.12 proper. +1 from my side, I think it's high time that we start thinking about planning the 0.12 release. Also, this will finally allow us to drop 2.3 for good. -- Remy
signature.asc
Description: OpenPGP digital signature
