I agree that a beta based on the current nightly build is a reasonable course of action for now.
My real regret is that we did not get a chance to cut a 1.1 release before the last wave of improvements came done the pipeline. My concern is that either the release-cycle will now be extended, while we absorb the new features, or will be rushed, just to move things along. Of course, Craig's work is consistently excellent, and the likelihood of any actual problems is slight to none. My underlying goal is to remind us that Struts is being used by some very serious teams on some very serious projects. These teams rely on the "#.#" release stamp to tell them that the codebase is ready for primetime, and it is our responsibility to ensure that it is. I would usually expect changes this significant to live in the nightly build for several months before release. But, keeping the other features out the hands of production teams is now bordering on cruelty. So, I guess, it comes down to "in for a penny, in for a pound"; are we ready to cut a beta? -Ted. "Deadman, Hal" wrote: > > I assume there will be at least one beta release of Struts 1.1 and a release > candidate after that. That will provide ample time to identify any specific > incompatibilities and address them. At least we will be able to identify the > exact cause of the incompatibility and then we can discuss a specific > problem rather than unidentified issues. > > It's too early to give up on the ideal solution which is not adding a second > package. A second package will cause grief similar to the struts-form.tld. > The periodic bug reports of people trying to use that taglib are annoying > but imagine the time the bug reporters wasted trying to use that taglib. It > probably would have saved the world some time if it had been removed prior > to 1.0. People using pre-1.0 Struts or pre-1.1 nightly builds should expect > to make some minor changes if they upgrade. Especially when the changes will > save them time in the long run. > > People moving from 1.0 to 1.1 are already in for some global search and > replace due to the commons stuff. They are also going to have to do some > extensive testing because a great deal of changes have been made, aside from > the Big check-in. > > Nobody needs to upgrade an application that is well underway with a > particular version of Struts. If they do upgrade then they need to examine > the migration issues and weigh the migration cost against benefits of the > new features. Hopefully there won't be any known migration issues that > aren't resolved during a beta release. > > Hal -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
