Will Sadkin wrote:
Hi Robin,
I know I've asked before, but could you pleeeeze give us some advanced
warning when you're wrapping up a version, so we can get patches to you
before the deadline; I have some that I've been working on that I would have accelerated had I known that you were preparing a new candidate.
Well the Preview builds I consider to be just snapshots of the current state of things, and don't really have a whole lot of planning that go into them. I just turn the crank when I feel like things are in good shape.
Also, FTR, about how many more of these do you anticipate before it becomes
a general release, and do you have any target for when that will happen?
Your message interrupted my typing of my next message about this, so I'll just write about it here instead...
My plan is to now shift into Release Cantidate mode, meaning that 2.5.1.x builds from this point on could potentially be a general release. If/when the wxPython-dev folks have tested an RC build and given a green light then I upload it (the same installers) to SF and make a general announcement. If there is no green light then we'll work on fixes, increment the build number and try again.
If there are no big problems with p8 then the 2.5.1.1 build could happen as soon as the end of next week or sometime the week after. But since I don't really do feature freezes that doesn't prevent your patches from getting in to the series if they are not ready in time for a particular build. Anyway, to put a schedule on it, let's say that anything I have in my inbox by Friday morning (Pacific time) will get into the next build. (If I'm not totally ready by Friday then I'll keep taking stuff until I am ready.)
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!