Don, I agree with you that a release should be scheduled sometime very soon. However, at this moment due to the latest changes I would suggest the following process:
1/ tag all dependencies (XWork2, Tiles2, Guice, CodeBehind etc.) 2/ make a release of the external dependencies (XWork2, Tiles2, Guice) 3/ document the new things 4/ make an alpha to be tested/played with at least the committers 5/ only after these push a beta/ga How does this sound to you? ./alex -- .w( the_mindstorm )p. On 11/21/06, Ted Husted <[EMAIL PROTECTED]> wrote:
My best vote right now would be Alpha. I'm trying to get up to speed with all the recent changes, but I wouldn't want to put something out there for other people to use until I"ve actually used it myself. -Ted. On 11/20/06, Don Brown <[EMAIL PROTECTED]> wrote: > We really, really, really need to get a release out there, even if was > determined to be beta. The snapshot system is unpredictable and > confusing for potential users, and really, users shouldn't be using them > anyways as they aren't "official" struts releases. > > Any showstoppers to a likely beta release? > > Don > > PS. I just deployed the snapshots off trunk to maven --------------------------------------------------------------------- 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]
