--- Etienne_Labonté <[EMAIL PROTECTED]> wrote: > I think I remember you saying you would release 1.2 ASAP after removing > all > the deprecated stuff. I would like that very much since I have to > comment > out a few deprecated things in 1.1 and build my own Struts.jar
No, 1.2 will include a move to commons-resources and other minor enhancements as well as removing the deprecated stuff. David > > Etienne > > -----Original Message----- > From: David Graham [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 11:13 AM > To: Struts Developers List > Subject: Re: [VOTE] Struts 1.1 Final Release > > > Moving forward, if someone were to start to add another enhancement > (or > > "product change") while another was already unreleased in the nightly > > build, I would veto the change and force a point release. (And if I > > didn't I'm sure someone else around here now would.) The justification > > > being that we simply don't have the resources to support releasing so > > many changes at once. > > Just for clarification, each enhancement doesn't need it's own release, > just major changes like moving to commons-resources. I see each point > release as having at most one major change and I will join Ted in > vetoing > any major changes occuring while another is in progress. > > I've personally signed up for about 10 minor enhancements to 1.2 and > will > help with the commons-resources move. When that move is done we should > cut 1.2. > > David > > > > > The other issue was moving dependencies to other products. We should > now > > > > make a point release before (or after) moving or adding any > > dependencies, even if it is to a Commons product. The next thing on my > > > radar is moving some dependencies to Commons Resources. So as soon as > we > > > > do that and the code seems stable, it should trigger a point-release. > > > > Since we are all volunteers here, what gets done depends on who is > > willing to actually do something. There is no hierarchy; individual > > committers decide what they want to work on, and then other developers > > chip in as they wish. But, we can each veto any product change we > > believe is technically unsound, which provides a check and balance. > > > > Most of us are working stiffs, so we tend to do things that we need > for > > our own applications. The vast majority of changes to Struts come > about > > from developers submitting patches they made so that their own > > applications became easier to write. > > > > -Ted. > > > > > > -- > > Ted Husted, > > Struts in Action <http://husted.com/struts/book.html> > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
