Default versions for ScalaCheck and ScalaTest pushed to 1.6 and 1.0.1, respectively (Bill just made the release). Three tests are failing in the ScalaTest specs, but I'm not sufficiently familiar with ScalaTest as to figure out what's going on (one of them just looks like a transient FSC failure).
Once we get these passing again (and assuming it's before Tuesday), I vote that we cut a new release candidate so we can get some more testing in before our deadline for JRuby 1.5. Daniel On Sun, Apr 18, 2010 at 11:10 PM, Alex Boisvert <[email protected]>wrote: > On Sun, Apr 18, 2010 at 8:44 PM, Daniel Spiewak <[email protected]> > wrote: > > > > > I thought about that, but I'm leery about holding up our release even > > longer. I wouldn't mind giving them one or two days, but any longer... > > > > How about this: we allow maybe two days waiting for JRuby 1.5. In the > > meantime, we test with the 1.5 RC to make sure there isn't anything that > > would trip us up. If 1.5 GA doesn't come out before Tuesday night, we do > > the 1.4 release without it. Once 1.5 comes out, we can test against it > and > > repackage the all-in-one distribution. If there are any bugs which crop > up > > because of changes from 1.5 RC to 1.5 GA, we can do a 1.4.1 (or perhaps > > 1.4.0.1) release at that time. I don't see this as a particularly likely > > scenario though, it seems like all we should need to do is repackage the > > all-in-one and we'll be golden. > > > > How does that strike everyone? > > > > Fine by me. > > alex >
