Charlie Groves wrote:
> Hi all,
> I committed an implementation of slots earlier today, and with that
> all of the language features for 2.2 are in. Now we need to figure
> out what needs to be done to actually release this thing. Here are
> the things I'd like to see happen before 2.2beta1:
> 1. Triage on the bug tracker.
> I know Frank went through the tracker back in May, and I've gone
> through it a couple times in the past few months, but it'd be good
> to make another pass to make sure nothing vital falls through the
> cracks. I'm going to do this tonight but a second pair of eyes would be nice.
> 2. Decide which test failures matter.
> Right now, we've got 18 failing tests in regrtest on trunk and another 6 at
> least that fail only on Windows(or at least they don't fail on Mac
> and Linux). At the very least I'd like to get consistency across
> the platforms and fix descr, new, weakref and zlib before making a beta.
notice the even PyPy is not passing all of descr currently, it contains
a lot of implementation details,
also I think the modified version we are using is a modified one from
2.3, not 2.2,
because some aspects of new-style classes (the MRO for example), were
kind of broken in 2.2,
this makes a difference only in corner cases, I didn't have the energy
to implement the broken
behavior to change it later, so for example the MRO is already the C3 as
in 2.3. We may have to disable
, skip some tests or change them to pass descr.
> 3. Come up with a post beta strategy.
> Basically, what releases should we make between this beta and
> 2.2. I figure it's been long enough between releases that we're
> going to uncover
> enough bugs in the first beta to require a second beta at least. We
> could also use the time in between to get the rest of the regrtest
> failures. So, we plan on a second beta, and if it
> does reasonably well, we start making release candidates until
> one sticks.
yes, we have a lof of changes in here, and also some of them from
intermittent bursts of coding
so testing is going to be very important, also our test suite is not
nil, but even for CPython
it is a known fact that a lot of aspects have no tests, so thirdy party
testing is going
to be very important.
> 4. Find appropriate phoenix or dead rising from grave artwork for the
> Need to get something up there to let people know we're back :)
> I'd like to put some work into the documentation before 2.2 proper
> comes out, but I feel like that can wait until we get people trying
> the beta. It seems like the installer has worked well for the recent
> snapshot releases, so I'm not too worried about that.
> Thoughts? Additions?
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> Jython-dev mailing list