> From: Joe Germuska [mailto:[EMAIL PROTECTED]] ... > From that, you'd think a 1.1 release was just around the corner!! > However, it's not going to be that easy. My Bugzilla query turns up > 39 non-Enhancement open bugs against Struts. Some of these are very > old and may no longer be relevant. (For example, a few refer to the > original File Upload piece, while Struts now uses commons-fileupload.)
After reading this, I took a quick look at Bugzilla. It seems that a lot of the bugs still marked as 'open' have actually had patches submitted. I don't know if this is because the patches were found to be incorrect, but I didn't see any comment to that effect during my quick trawl. So maybe the problem is that bugs just aren't being closed when they're fixed. > That said, Struts components like Tiles, Validator, and most > recently, the EL version of the tag libraries were all dreamed up by > someone who saw a need, and they were adopted into Struts because > those people committed their own energy to making something happen. Because of all these having been incorporated, I think Struts is now way past something that should have been called a 1.1 release. According to the release plan document, 1.1 beta 2 was supposed to be feature-complete; the intent was to provide a stable base for bugfixes and documentation updates, leading to the 1.1 final release. As someone pointed out earlier in this thread, now that all of this additional (wonderful!) functionality has been added it's much more like a 2.0 release. > From: <[EMAIL PROTECTED]> ... > >The Release Plan page on the Jakarta site lists the bugs which are > >officially targeted for a 1.1 release. However, it's pretty out of > >date. Perhaps turning this into a living document would be a good > >volunteer opportunity? > > I think this is a good idea - would be somewhere where people could just go and know > that they an clear and accurate picture of the current release status, which they > can take back into their discussions. Do others agree, and that this is possible and > practical? I definitely agree that this would be useful. I would prefer it to go slightly further though, into being a milestone plan along the same lines as the one Mozilla has (i.e. to set out the features and bug fixes that are targetted for the next N releases, rather than just the next one). I find that gives a very clear picture of where the project is at. It does need to be kept up to date, though... Vil. -- Vilya Harvey, Consultant [EMAIL PROTECTED] / digital steps / (W) +44 (0)1483 469 480 (M) +44 (0)7816 678 457 http://www.digitalsteps.com/ --Disclaimer-- This e-mail and any attachments may be confidential and/or legally privileged. If you have received this email and you are not a named addressee, please inform the sender at Digital Steps Ltd by phone on +44 (0)1483 469 480 or by reply email and then delete the email from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this email. Although Digital Steps Ltd routinely screens for viruses, addressees should check this email and any attachments for viruses. Digital Steps Ltd makes no representation or warranty as to the absence of viruses in this email or any attachments. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
