Guys,
I think the subject of this thread shd be what is the subject of
this mail for help of others and not as was before.Hope you all agree with
me on this. Craig thanks a lot for clearing the confusion. One more thing
the thread started with the usage of javascript with struts1.0.2.Any
suggestions there?
Thanks in advance!
Regards,
Taati
> -----Original Message-----
> From: Craig R. McClanahan [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 13, 2002 6:20 PM
> To: Struts Users Mailing List
> Subject: RE: javascript and struts1.0.2
>
>
>
> On Mon, 13 May 2002, Galbreath, Mark wrote:
>
> > Date: Mon, 13 May 2002 17:56:56 -0400
> > From: "Galbreath, Mark" <[EMAIL PROTECTED]>
> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> > To: 'Struts Users Mailing List' <[EMAIL PROTECTED]>
> > Subject: RE: javascript and struts1.0.2
> >
> > Craig,
> >
> > 1.0.2 may be the "standard production release," but it was obsolete the
> > moment 1.1b-1 was released. I wouldn't encourage anyone to build
> > applications with it.
>
> As should be obvious to everyone, Mark is speaking for himself here.
> Don't listen to this advice ;-).
>
> If you are adventerous, or your application isn't going to need a stable,
> production quality, Struts implementation right this second, feel free to
> build against 1.1-b1 (assuming you can talk any involved pointy-haired
> bosses to accept code with a "beta" label).
>
> If you must have a stable, production quality, Struts imlementation right
> this second, you'd be nuts to use the new version -- stick with the tried
> and true version.
>
> > As far a the definition of "beta" being the feature
> > list is frozen, that simply is not true in most cases, though you may
> have
> > decided it in this case. "Beta" software, by definition, is distributed
> to
> > a select group in order to elicit feedback not only on bugs, but on
> features
> > that should be added and/or removed.
> >
>
> You might want to take a look at how Apache projects actually operate
> (which is pretty typical of most open source oriented projects as well).
> In particular, betas are not restricted-distribution things -- they are
> labelled "beta" to properly set expectations about quality and feature
> completeness.
>
> Commercial software organziations may well follow different policies ...
> but "them" is not "us". :-)
>
> > Of course, that's just my opinion; I could be wrong.
> > (apologies to Dennis Miller)
>
> If you care what the authors of the code (i.e. Struts committers) think,
> then you are definitely applying your own definitions to our words, not
> using them for what *we* say that they mean.
>
> Struts 1.0.2 is the one and only current production release of Struts.
>
> Struts 1.1-b1 is a beta release of what will be the next version. It's
> there to encourage testing and shake out bugs, so that we can make it the
> next production release when it is ready.
>
> Note that, even after 1.1 goes final, 1.0.2 will not be "obsolete" --
> there are thousands of applications in the world running on it. Not
> everyone can upgrade at the drop of a hat, no matter how many cool
> features are in the new version. And, if there happen to be enough
> serious bugs that need a fix, it's not impossible to conceive of a 1.0.3
> or 1.0.4 release to protect the investments of anyone who cannot (for
> whatever reason) move immediately to 1.1.
>
> > Mark
> >
>
> Craig
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
