On 2/16/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > > On Thu, February 16, 2006 12:34 pm, Martin Cooper said: > > As for 1.1, personally, I _do_ see 1.2 as making 1.1 "obsolete", so I > > don't > > see a need to update that as well. And I would expect 1.3 to make > > 1.2"obsolete" in time, too. > > I don't disagree, but isn't it true that 1.3 won't make anything obsolete, > the WW merger will? I mean, one could almost at this point ask what's the > point of putting 1.3 out at all, given that the WW merger is the future of > Struts, right?
You'll note that I put "obsolete" in quotes. What I mean is that I see no reason that anyone would want to start a new project using 1.1 when we have 1.2 GA releases. Similarly, once 1.3 goes GA, it doesn't make much sense to start a new project with 1.2. Beyond that, it's a matter of how many versions we want to (and have the energy to) support. The WW merger won't make anything obsolete by itself. It will provide a new choice for people to use on their projects, and we hope to encourage them to migrate to the new Struts 2. Yes, this will eventually make the Struts 1 line obsolete in a more real sense, but the Struts 1 line is not going to go away for a very long time. As for the point of releasing 1.3 at all, which I think you are actually asking rather than almost asking, ;-) it brings a new way of working with the Struts 1 line, and a new way of customising it, that could be highly beneficial to many developers. I know that I'm not about to back off to 1.2.8 on my current project, since I'm getting a lot out of 1.3, but I'm also sufficiently invested in that that I'm not about to switch horses and move to WebWork instead. Now, I could be alone, but I strongly suspect I'm not. ;-) -- Martin Cooper > -- > > Martin Cooper > > Frank > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
