On 2/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Putting out a release just encourages developers outside of the > circle of committers to make that value judgement.
Quite right. If we were talking about an API that we introduced into the nightly build last week or last month, then I think we could be more cavlier with changes. But much of the new API has been in the nightly bulid for well over a year now. At this point, all we have done is tag the repository. We posted a test build of Action, but we haven't "released" anything. Now, we are in position to decide if we do want to release the API we already have, or if we want to continue to make changes and refinements. When we make those decisions, we can now make them against a known reference point: the STRUTS_ACTION_1_3_0 tag. As we make changes, we can now document those changes in the notes, so that those of us with a nightly build in production can prepare for any API changes between 1.3.0 and 1.3.1, and the other milestones that are sure to follow. Also, those of us with an arbitrary nightly build in production might choose to deploy the 1.3.0 build, so we are all working from the same page. -- HTH, Ted. ** http://www.husted.com/ted/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
