On 12/14/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
On Dec 14, 2006, at 9:22 AM, Wendy Smoak wrote:
> Whether to release "the framework" together or in pieces is just > something we need to decide, figure out how to communicate to users, > and then adjust the build to match. Sounds like that decision is the next logical step then. If we went with separate releases for each artifact does that just involve removing the modules from the shale-parent POM?
For the record, I'm for "together". While there are some good arguments for releasing components individually, and it might even be easier from a technical standpoint, I think we'll have problems explaining it to users. (I remember not wanting to announce a new release of the struts-core jar because I couldn't figure out how to word it without making it sound like *all* of Struts 1.3 was ready.) And if all else fails, I'll fall back on the "be like Spring" argument. :) On a related topic, I think if we're going to do the 'tag it, build it, and vote on quality later' thing, it has to be okay to 'skip' version numbers. (Something IIRC Craig and Sean said they were not in favor of.) For example, at Tomcat they routinely discard a version number or two in the process of getting the next build out. After 5.5.20, the next version available to users might well be 5.5.23. It doesn't cause any problems there. With that, and some more automation from Maven-land, we could get in the habit of more frequent tagged builds, which means more chance of promoting one of them to GA. (I'm hesitant to predict that we've got it right after only four, especially with all the recent changes.) -- Wendy
