The first pass is complete. Here's where we stand:
JRuby 1.0.2: 54 scheduled
JRuby 1.1: 147 scheduled
JRuby 1.x: 7 scheduled
71 unscheduled
Many of the open bugs including most of the unscheduled bugs, are
awaiting followup from submitters. They'll likely get punted if there's
no followup, so please scan them.
It's unlikely we'll fix that many issues for 1.0.2, since we want to try
that release out in the next two weeks. Plan accordingly for that, and
make noise/submit patches if you have a bug in the 1.0.2 column you
really want fixed. Do the same if you have a bug not scheduled for 1.0.2
that you really need.
We'll fix what we can for the 1.1 beta release at RubyConf next weekend,
and as much more as possible before a final release toward December.
Again, if you have a bug in there, the best way to ensure it gets fixed
is to submit a test case and hopefully a patch.
We'll start doing a second pass over the 1.0.2 bugs late this week, and
punt what we can't fix to 1.0.3. Ditto for 1.1b and 1.1 final.
- Charlie
Charles Oliver Nutter wrote:
I went through about a 120 bugs this evening, fixing a bunch, applying
patches for a bunch, closing a bunch that were already working,
backporting a few fixes, assigning some to specific versions or
committers, and adding various comments.
Those of you on the JIRA mailing list will have gotten a lot of
spam...sorry about that. But for all of you that have reported issues,
please check over your issues and see if there's any follow-up required.
A bunch had patches but were missing tests. Some had almost no
information or needed at least a little more digging. Others, I couldn't
make heads nor tails of.
I got as far as JRUBY-1248 counting down...I'll try to continue early
next week.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
