On Fri, May 1, 2009 at 11:30 AM, Howard Lewis Ship <hls...@gmail.com> wrote:
> > > > > > 4) Stability - you need to lay down a road map that shows management and > > developers that they can count on a stable environment for the > foreseeable > > future. Howard, T6 can't be so different from T5 that you have to > rewrite > > apps. Tapestry has a bad reputation and if you want general adoption, you > > personally have to assure everyone that the days of major changes in the > > framework have ended. > > Now you are citing yourself as a newbie. Anyone who's followed this > mailing list has seen Tapestry 6 come up and everyone, including > myself, strike it down. Sure, there's a couple of things that I'd do > differently now, but not enough to address the kind of effort involved > in yet another rewrite. Again, 5.1 is a demonstration of the future > path, where new features can be added non-disruptively. > > > Well the issue of version numbers is always a case of shifting sands. One person's point release is another's major version. Certainly Tapestry will continue to improve, over time. The version numbers will continue to increase.. and at some point version 5.9.9 will yield. ;-) Or perhaps we'll stay at 5 for the foreseeable future, in which case, the point change from 5.x to 5.y becomes a major set of feature enhancements. I don't want to argue that point, I just want to say that I've been doing work with tapestry since 2005, so I may be a newbie to the list, but I've had to support the choice of Tapestry in a variety of circumstances. Stability is a concern when trying to convince an organization to adopt a technology and one that's not been helped by major changes in architecture. Also one that can only be addressed by time. Now as far as funding documentation is concerned. Yeah, that's the problem isn't it. Who pays, who does the work, where does it happen. I have the good luck right now, of being like the the consultants in that old commercial by UPS professional services. The one where two consultants propose a plan for improving upgrading and streamlining a company's business process and the CEO says. "Ok, great I love this plan let's do it!". At which point the consultants start to laugh... "Dot it? Do it!, We don't DO the work, we just tell you what needs to be done." :-) At some point, I'd be happy to contribute some hours to a task like that, but at the present moment, my own chaotic life has my full attention. Tony
