Frank Wierzbicki plans to release another soft beta 3 later this weekend, possibly Sunday. In the meantime, I would encourage anyone here to build what is in trunk and run the unit tests, just so we haven't missed anything. (The unit tests can be flakey. Build twice if necessary :)
One observation I would make is that informal processes like discussing a bug on this list, which helps with prioritization, can work better when we also have a submitted bug in bugs.jython.org
, a patch that can be directly applied, and the patch includes relevant tests. As we work through beta 4, this will be increasingly important. As an alternative, pull requests against https://bitbucket.org/jython/jython
- with relevant tests - also work, although they should never use a new branch - this breaks pushing into hg.python.org/jython
and require some manual munging to fix. I don't want to discourage anyone from submitting a patch or using pull requests, because that can often be very helpful regardless if we can directly apply, but I did want to explain why it can be slower than we all would want.
Lastly, I would like to mention I did some "spring cleaning" of the bugs in bugs.jython.org
, reflected in this week's stats:
Issues counts and deltas:
open 328 (-34)
closed 1845 (+41)
total 2173 ( +7)
This weekend we commemorate Memorial Day in the United States with a long weekend. I look forward to kicking off the summer, running in the Bolder Boulder 10 kilometer race with my family, and taking a short break from Jython development until Tuesday.