Jim Gallacher wrote:
Gregory (Grisha) Trubetskoy wrote:
I thought may be putting together a release schedule would help making
3.2 closer to reality.
I would really like to see it out some time before the next ApacheCon
US (10-14 December). I've submitted a mod_python talk and if it gets
approved, it'd be nice to be able to discuss the new/fixed things in 3.2.
Just to remind everyone how a release works - first a tar file is
produced, which is announced only on the list. A few people on the
list (3 or more preferabley) need to test it and send in their +1's
(or -1's). If all is well, the file is released to the public, else we
repeat this cycle.
I think that 3.2 should initially be relased as 3.2.0 beta, with a
plan to release 3.2.X as stable a few weeks later.
Make sense to me.
And of course I really meant "Makes sense to me". :)
Assuming that the release iteration will take 3 weeks (this is a worst
case scenario),
Aug 15 3.2.0b private release
Sep 7 3.2.Xb approved for public release
Nov 7 3.2.Y private release
Nov 15 3.2.Y public release
[I'm using X and Y since we don't know what those numbers may be]
The Sep 7 - Nov 7 is a month for public testing of 3.2.Xb.
Does this sound like a plan?
This schedule looks good to me. I've been putting the finishing touches
on the docs for FileSession. (And making a couple of changes to
Session.py so that the code matches the docs ;) ). Should be done in 30
minutes.
In true (Monty) Python fashion you need to multiply everything I say by
10. (Or is it 20?).
Anyway, I've committed the documentation for FileSession. There are
still some rough edges in the docs I'd like to fix (more examples, a bit
of a blurb explaining exactly what session lockings is all about) but
nothing earth shattering, and not important enough to hold things up any
further.
I'm good to go for a beta release.
Regards,
Jim
