>>But, the original question was about the sidebar menu. Those are links
to the archival copies for GA releases, not every incidental beta that
we release.
If this were true, there would be no 1.2.x link on the sidebar menu. 1.2.9 was
the last GA release, which means anything after that is a snapshot or some beta
release.
So I ask: why is 1.2.x given preference (a version without a label or vote),
but not 1.3.5 (versioned and voted)?
Paul
Ted Husted <[EMAIL PROTECTED]> wrote: On 8/18/06, Paul Benedict
wrote:
> I'll take the correction, but I don't understand it. We released a product
> and voted it beta --
> a beta release? :-)
As mentioned in another message, we can in fact have beta releases.
But, the original question was about the sidebar menu. Those are links
to the archival copies for GA releases, not every incidental beta that
we release.
We can mention the 1.3.5 beta on the welcome page, download page, and
announcements page. Should it passses the GA muster, then we will
archive the documentation for future reference. (Which is when it gets
a link on the sidebar.)
It's very important to remember that Struts applications tend to have
long life cycles. Nearly all the teams I meet with standardardized on
Struts 1.1. Many other teams are using Struts 1.2 in production, and
may not migrate to Struts 1.3 or 2.0 for many months, or years, or
ever.
We maintain archives of the GA releases for everyone's use and
benefit. (Mostly our own, since it's handy for answering questions
people have about legacy GA releases.) Should 1.3.5 make GA, we will
archive i's documentation too.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
countries) for 2ยข/min or less.
