There would be no reason for it to take longer. Along with WW-1747, there are a number of quick and harmless fixes on the 2.0.7 TODO list. Given something to put in the release notes, I'm up for rolling a milestone on any given Sunday.
And, honestly, if this issue has been lurking for so long, undoubtedly, there are going to be others. But, we are not going to catch those until more people try the product. At this point, I don't believe we are going to hook many more people with beta releases. The best strategy might be to prepare for a succession of bi-weekly milestones, which would hopefully proceed directly to GA. Of course, in the meantime, the trunk is open for 2.1.x development.
From prior discussions, the big tickets there seem to be extracting
Ajax/Dojo and portlets to plugins. IMHO, those changes alone would be enough to get stared on the next series. -Ted. On 2/21/07, Rene Gielen <[EMAIL PROTECTED]> wrote:
After all, if we plan to push out a 2.0.7 within one or two weeks after doing 2.0.6 GA, the problem might not be that big. But if it takes longer, I would still vote for not labeling 2.0.6 for GA. - Rene > > On 2/21/07, Rene Gielen <[EMAIL PROTECTED]> wrote: >> >> Am Di, 20.02.2007, 16:17, schrieb Nate Drake: >> > [X] Beta >> > >> > >> > Due to WW-1747. >> > >> >> Finally, WW-1747 and the related issues should be fixed now. We've now >> got >> additional tests in place for all reported issues, and they all pass >> (yes, >> even no broken build 8-). >> >> My vote is >> >> [x] Beta >> for 2.0.6 as is >> >> [x] GA >> for 2.0.6 with WW-1747 patch included (2.0.7 ?) >> >> Regards, >> - Rene > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
