Robin,
since I have a coding sprint for PythonCard coming up October 23-24 in Bellevue (that's Seattle for those of you that don't live in the area) I want to get another release out the door before then so people don't have to work from cvs. Since PythonCard is tracking the latest and greatest wxPython I'm wondering whether I should just go with 2.5.2.8 or whether you expect an imminent 2.5.2.9 in the next week or two?
Robin,
since I have a coding sprint for PythonCard coming up October 23-24 in Bellevue (that's Seattle for those of you that don't live in the area) I want to get another release out the door before then so people don't have to work from cvs. Since PythonCard is tracking the latest and greatest wxPython I'm wondering whether I should just go with 2.5.2.8 or whether you expect an imminent 2.5.2.9 in the next week or two?
If the C++ guys stay on track then there will be a wxWidgets 2.5.3 released this weekend or maybe the next. I expect to have wxPython 2.5.3 within a week or so after that.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I assume you mean the first daily build for us to start testing. Typically, when we've moved to a new branch it takes us a few weeks at a minimum or in some cases months before a public release is done. If everyone else thinks the changes between 2.5.2.8 and the current 2.5.2.9/2.5.2 branch warrant another release before we dive into 2.5.3 then I would support doing that based on the changes listed below.
I doubt it will require much testing on our part before a public release. I have been running the regular build on my Mac and Windows boxes since it came out and plan to try the unicode build soon to workout some resource load and save issues in PythonCard (e.g. saving as Unicode Python strings and loading in a non-Unicode build or vice versa).
ka
···
On Sep 30, 2004, at 11:17 AM, Robin Dunn wrote:
Kevin Altis wrote:
Robin,
since I have a coding sprint for PythonCard coming up October 23-24 in Bellevue (that's Seattle for those of you that don't live in the area) I want to get another release out the door before then so people don't have to work from cvs. Since PythonCard is tracking the latest and greatest wxPython I'm wondering whether I should just go with 2.5.2.8 or whether you expect an imminent 2.5.2.9 in the next week or two?
If the C++ guys stay on track then there will be a wxWidgets 2.5.3 released this weekend or maybe the next. I expect to have wxPython 2.5.3 within a week or so after that.
Robin,
since I have a coding sprint for PythonCard coming up October 23-24 in Bellevue (that's Seattle for those of you that don't live in the area) I want to get another release out the door before then so people don't have to work from cvs. Since PythonCard is tracking the latest and greatest wxPython I'm wondering whether I should just go with 2.5.2.8 or whether you expect an imminent 2.5.2.9 in the next week or two?
If the C++ guys stay on track then there will be a wxWidgets 2.5.3 released this weekend or maybe the next. I expect to have wxPython 2.5.3 within a week or so after that.
I assume you mean the first daily build for us to start testing.
Yeah.
Typically, when we've moved to a new branch it takes us a few weeks at a minimum or in some cases months before a public release is done.
I don't think it will take that long this time as I've been following the C++ check-ins very closly with wxPython updates (except for a couple things I decided to wait on because they are not settled in wxWidgets yet,) so basically the 2.5.2.9 test builds are *very* similar to what 2.5.3 will be. Also most of the stuff in CHANGES.txt is bugfixes and I've only had to make one entry in the Migrarion Guide since the last release. (Although it looks like there might end up being one or two more *minor* migration issues by the time 2.5.3. is done.)
Anyway, if we find via our test builds that there issues that would require changes in the C++ after 2.5.3 I would rather that they wait until after the first wxPython 2.5.3.x release because I've promised some folks that there would be a 2.5.3.x of wxPython that could be built with the stock 2.5.3 of wxWidgets. We can still do a 2.5.3.x+1 later if needed.
···
On Sep 30, 2004, at 11:17 AM, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
1) it would be helpful to have an official v2.5.2.9, and
2) I'm pessimistic about the timetable of wxWidgets v2.5.3.x, esp. considering both past history and the current state of the wxWidgets bugbase.
To this I would like to add the following:
1) I can appreciate the about of work that goes into turning the crank for any release. Making an official v2.5.2.9 may not have much interest for the wider group of wxPython consumers.
2) keeping up with wxWidgets and finding a good cutoff point for building an official v2.5.2.9 may not be feasible, given the current level of activity in the wxWidgets tree.
3) perhaps converting the latest preview release into an official build would be a solution?
Regards,
David S.
···
================
Robin Dunn wrote:
Kevin Altis wrote:
On Sep 30, 2004, at 11:17 AM, Robin Dunn wrote:
Kevin Altis wrote:
Robin,
since I have a coding sprint for PythonCard coming up October 23-24 in Bellevue (that's Seattle for those of you that don't live in the area) I want to get another release out the door before then so people don't have to work from cvs. Since PythonCard is tracking the latest and greatest wxPython I'm wondering whether I should just go with 2.5.2.8 or whether you expect an imminent 2.5.2.9 in the next week or two?
If the C++ guys stay on track then there will be a wxWidgets 2.5.3 released this weekend or maybe the next. I expect to have wxPython 2.5.3 within a week or so after that.
I assume you mean the first daily build for us to start testing.
Yeah.
Typically, when we've moved to a new branch it takes us a few weeks at a minimum or in some cases months before a public release is done.
I don't think it will take that long this time as I've been following the C++ check-ins very closly with wxPython updates (except for a couple things I decided to wait on because they are not settled in wxWidgets yet,) so basically the 2.5.2.9 test builds are *very* similar to what 2.5.3 will be. Also most of the stuff in CHANGES.txt is bugfixes and I've only had to make one entry in the Migrarion Guide since the last release. (Although it looks like there might end up being one or two more *minor* migration issues by the time 2.5.3. is done.)
Anyway, if we find via our test builds that there issues that would require changes in the C++ after 2.5.3 I would rather that they wait until after the first wxPython 2.5.3.x release because I've promised some folks that there would be a 2.5.3.x of wxPython that could be built with the stock 2.5.3 of wxWidgets. We can still do a 2.5.3.x+1 later if needed.
1) it would be helpful to have an official v2.5.2.9, and
2) I'm pessimistic about the timetable of wxWidgets v2.5.3.x, esp. considering both past history and the current state of the wxWidgets bugbase.
I'm fairly confident that it will happen, but we'll see.
To this I would like to add the following:
1) I can appreciate the about of work that goes into turning the crank for any release. Making an official v2.5.2.9 may not have much interest for the wider group of wxPython consumers.
Doing the actual builds and uploads is almost toally automated now. The only downside is that it raises the temperature in my office about five degrees... The tricky part is making sure that everything is ready for an official build, but even then there are some issues to doing a 2.5.2.9 now, see below.
2) keeping up with wxWidgets and finding a good cutoff point for building an official v2.5.2.9 may not be feasible, given the current level of activity in the wxWidgets tree.
I would either have to backup several days in CVS and make a branch (and lose the newest bugfixes and such,) or I would have to wait until I'm finished with what I am currently working on before a 2.5.2.9 could be done. And even if I do that the version numbers have already been changed in wxWidgets so I would have to branch those files if I want to be able to tag the 2.5.2.9 release in CVS... That doesn't seem worth it if there is a 2.5.3 release this weekend because it will end up being almost identical to 2.5.3.
3) perhaps converting the latest preview release into an official build would be a solution?
That's possible but it would take a little surgery on the tarball to adjust the version numbers and then a rebuild of everything. But I would not be able to go back and and tag the release in CVS because I didn't make a tag when the test build was done.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!