I've noted, with some dismay, discussion of making major infrastructure
changes to 1.1 pre-release. Now, as much as I'll admit I've snuck a few
new features in under the wire, the levels of destabilization (and
delay) being proposed (especially in regards to gutting the Resource
subsystem) worry me.
I'm talking to a potential client right now who has held off on moving
to 1.1 "because it's beta." I'm sure we all know companies with the
same attitude. All the nice new toys of 1.1 won't do us as developers
much good until we can deploy them at clients.
There comes a time to drive a stake in the ground where ever you are,
and call it a release. I'd like to propose that, modulo any critical
(and I mean show-stopper) bugs, we're there.
We all know that 1.1 has been a "Real Soon Now" release for a good long
time now. If we want people to adopt it (or move off of 1.0), it has to
lose the beta tag.
I'm the new fish in the pond here, but I wanted to put in my +1 for
sticking a fork in the puppy, 'cause it's done.
James Turner
Owner & Manager, Black Bear Software, LLC
[EMAIL PROTECTED]
Author:
MySQL & JSP Web Applications:
Data Driven Programming Using Tomcat and MySQL
ISBN 0672323095; SAMS, 2002
Co-Author:
Struts Kick Start
ISBN 0672324725; SAMS, 2002
Forthcoming:
Java Server Faces Kick Start
SAMS, Fall 2003
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
