"Steve Peterson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > While you are talking about updating the build, another small item for the > todo list would be to sync the version number assignment up with the > now-project-standard a.b.c style release numbering. I have personally seen > some (small) confusion related to release 1.1.0 being stored in > jakarta-struts-1.1.zip.
The problem here, I think, is that we should not be referring to it as 1.1.0 at all. The decision we made, unless I'm mistaken, is that we would start to use the 3-part numbering *after* Struts 1.1, not *with* Struts 1.1. So there is no 1.1.0 release. -- Martin Cooper > > S > > At 08:14 AM 7/22/2003 -0400, Ted Husted wrote: > >Craig R. McClanahan wrote: > >>Do we really want to wait that long? CAN we wait that long? > > > >How long is a piece of String. =:0) > > > >We can do a 1.2 release candidate this month, and then figure on doing 1.3 > >by the end of August. > > > >As long as week keep 1.x.x in evolutionary mode, I don't think we need to > >worry too much about maintaining branch for 1.#.x versus 1.#.x. In > >practice, the 1.1 branch has been out-there for over a year, and it seems > >unlikely that any serious problems could be cured with a trivial > >point-release fix. We just have to be careful to keep the HEAD > >release-ready and whiteboard anything radical before merging it in. > > > >I have family coming in this week and can't volunteer to roll 1.2 myself > >this weekend. But if no one beats me to it, I'd like to roll a 1.2 release > >candidate the first weekend in August. > > > >-Ted. > > > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
