We have a few options on 0.8 right now, and I wanted to toss them out to
see if there are strong opinions either way. Any code changes require
further beta testing, and therefore more time before final release of 0.8.
Here are the options I put forward to consider:
a) Release 0.8 right now, without the mkstemp fix or any recent
patches, but with updates to the version numbers in the
documentation.
b) Put out 0.8b3 with the mkstemp fix that Geoff checked
in a few days ago. Let this sit out for a couple days
to verify the mkstemp fixes.
c) Put out 0.8b3 with the mkstemp fix, and a couple of
other minor patches. Let this sit out there for a couple
more days to verify.
Geoff had asked if someone could test the mkstemp fixes he applied to
the trunk under Linux. Has anyone had a chance to do this?
I like the idea of providing compatibility with Python 2.3 even though
it is only in alpha. But this requires at least a few days as a short
beta cycle.
My leaning right now is to go with option (b), puting out 0.8b3 tonight
with only the mkstemp and documentation changes from 0.8b2. Then over
the weekend, roll the version numbers and release 0.8 unless there are
problems specific to the 0.8 beta changes.
Any comments?
-Stuart Donaldson-
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
- RE: [Webware-devel] 0.8 beta status. Stuart Donaldson
- RE: [Webware-devel] 0.8 beta status. Geoffrey Talvola