An additional week or two for me means that I can, 1) review the Eclipse task, add test cases and maybe merge BUILDR-17 2) review and add some Scala-related documentation 3) test backward compatibility with a few projects currently using 1.2.x
So I think it's worth it to improve the quality of 1.3. alex On 2/1/08, Assaf Arkin <[EMAIL PROTECTED]> wrote: > > I was hoping to have the 1.3 release today, but apparently that won't > happen. Best guess we're a week/two away. > > Most of the new features are coupled to implementation changes, which is > why > we're calling this a 1.3 release. It will not be as stable as 1.2.10, but > I > do want to make sure it's stable enough to be an official > release. There's > still a few loose ends that need to be tied. > > Besides code, there's also improvements to the documentation, and covering > the new features. And here too there are still a few unfinished tasks. > > Since 1.3 is the next upgrade from 1.2.10, I feel it's important to make > sure it's backwards compatible, so I'm spending some time on testing that. > If you can tell me you're successfuly using 1.3 instead of 1.2.10, that > will > help. I also expect to close all outstanding bugs filed against 1.2.10. > > There's a few new features brought up on the mailing list recently. They > are not part of the original 1.3 plan, which was all about multi-lingual > support and later expanded to include JRuby support. My fear is that if > we > keep adding features, we'll never have a 1.3 release. And keep in mind, > once 1.3 is out we'll start working on 1.3.x. These points releases are > easy to roll out, I don't mind making a few of those to introduce new > features. > > > What's your take? > > Assaf >
