Nicolas Lehuen wrote:
Well, why not keep our plan of releasing 3.2 ASAP and save this
problem for a later 3.2.x as a bug fix ?
Making subsequent bug-fix releases should be fast and easy. We cannot
afford to repeat the long hiatus between 3.1.3 and 3.2, with a long
period of time without any official bug fix.
I agree that 3.3 may come later, but we definitely should be able to
release 3.2 bugfixes version as often as possible. This will save us
and our users a lot of time, allowing us to stop writing "yeah, we
know this bug, it's already fixed in SVN but you'll have to wait an
undefinite time for the fix to go public".
+1
It's always tempting to make one last change, fix one more bug, but then
the release never happens. I think everyone has the will to move
mod_python forward, we just need a little more discipline. There are
lots of things we can do in 3.3, but I for one am not motivated to work
on these until 3.2 is out. Lets get this puppy out the door and then
have a discussion on plans and priorities for 3.3 with a view to
reducing the time between bug fixes and major releases.
Jim
Releasing often may need a bit of work on the web site side, however.
I feel that updating the web site is the current bottleneck, since
only Grisha can do it. Could it be possible to make the web site
writable by the commiters ? Maybe have a "web" directory in
subversion, so that we can edit the site and make update on the web
server side when we want to release new content ?
Regards,
Nicolas
2005/9/8, Graham Dumpleton <[EMAIL PROTECTED]>:
Jim Gallacher wrote ..
Gregory (Grisha) Trubetskoy wrote:
I've been away this weekend - just got back, but I'm too busy to try
to
read all the multiple-interpreter related comments. I guess my question
is - can someone provide a quick summary of how far we are from 3.2.1b
test tarbal?
I've also been away for the weekend. The patch for MODPYTHON-77 from
last Thursday was causing apache to segfault and I have not had a chance
to try the lastest changes from Boyan.
As Graham stated on the weekend, "the use of thread states can be very
tricky". I think we should proceed with the 3.2.1b without the fix. That
way we can take the time to make sure we understand the issues and fix
it in 3.3.
If we feel that 3.3 could be a while in coming, I'm tending to think that this
change to support use of extensions using the simplified GIL interface
should be incorporated into 3.2. This would depend though on how many
more beta snapshots we think we might go through.
Graham
