On the thread, Bill said he would do the release last week. I think Alex could try to give him a nudge. And if that doesn't work, we should go with Daniel's idea.
OK with that ? Antoine On Sat, Apr 17, 2010 at 22:29, Daniel Spiewak <[email protected]> wrote: > My vote: push the default ScalaCheck version forward to 1.6. This is > compatible with Specs 1.6.2 and Scala 2.7.7, the latest versions of each. > We would of course have to add a note to the documentation in the ScalaTest > section mentioning that ScalaCheck support requires the explicit use of > Buildr.version['scala.check'] = '1.5'. > > The only other option is to leave things as they stand, which is to keep > ScalaCheck compatible with ScalaTest by default and add the note to the > Specs section. The only difference is that ScalaTest 1.0 is not > *officially > * compatible with Scala 2.7.7 (nor is ScalaCheck 1.5, for that matter), so > we would be deliberately choosing to hobble Specs for the sake of a library > which simply hasn't kept up with the release cycles. If that is the > consensus then I'm ok with it, but we should be conscious of the fact that > we are actively choosing one "default supported" version over another, and > (if we choose to leave things as they are) that version also implies an old > version of Scala itself (2.7.4). > > In either case, a little more documentation is required, detailing what a > user would have to do to use ScalaCheck with either ScalaTest or Specs > (whichever becomes the unsupported option). > > Daniel > > On Sat, Apr 17, 2010 at 10:57 PM, Antoine Toulme <[email protected] > >wrote: > > > Ok so I guess our release is blocked by that item. > > > > That's the last critical bug we have I think. > > > > I propose that we release as soon as we have that in check. Thoughts ? > > > > On Sun, Apr 11, 2010 at 14:53, Alex Boisvert <[email protected] > > >wrote: > > > > > On Sat, Apr 10, 2010 at 11:28 AM, Antoine Toulme < > > [email protected]>wrote: > > > > > >> We're down to 5 open issues. > > >> > > >> > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310734&fixfor=12313152&resolution=-1&sorter/field=priority&sorter/order=DESC > > >> > > > > > > BTW, I've reported the issue about ScalaTest + Specs/ScalaCheck here: > > > > > > > > > http://groups.google.com/group/scalatest-users/browse_thread/thread/a429b4adf551278d# > > > and waiting for an updated release of ScalaTest. > > > > > > (I can't comment on Jira right now since it was hacked earlier this > week; > > > waiting for my account to be reenabled). > > > > > > alex > > > > > > > > >
