Yes, you are missing my original point #2 - "We need to be able to do "alpha" releases to get new, experimental features into the community for testing." I need a way to create an alpha release for 2.1 to hand off to our community for feedback, but if all releases require a unique patch version, I'm forced to create 2.1.1, 2.1.2, 2.1.3, etc.
Public API changes take a while and lots of feedback to really get right, so going six months without a release is not acceptable, IMO. Don On 2/22/08, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > Don Brown wrote: > > On 2/22/08, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > > > >> > These two points, put together, will necessarily result in a 2.1.0 > >> > release that is drastically different than 2.1.1. I just don't see > >> > any way around that. > >> > > >> > >> Tooling can solve this issue. > >> > > > > How? As I said, it is not possible for Struts releases to be > > compatible across patch versions. How will tooling solve this? > > > > I'm confused as to why it is not possible for them to be compatible. > Compatibility is part of software engineering and up to the developers. > Tools can perform static code analysis prior to releasing a patch > version and determine if APIs have changed. I would envision this type > of process: > > 1. Everyone tries their best not to bork 2.1.x > 2. The release manager for 2.1.2 (for example) runs the tool to check > public APIs against the 2.1.1 tag and trunk in SubVersion. > 3. If the tool passes or the errors seem acceptable to the release > manager, they do the release. > 4. If the tool finds errors and the errors look bad, release manager > halts release and tells developer that made said changes to fix them. > > Am I missing something? > > > -bp > > --------------------------------------------------------------------- > 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]
