Its more on encouraging users to move to releases where bug fixes and
security vulnerability fixes have been made.
From the ancient Struts 1.2.0 release notes:
The /vote/ may also serve to /reclassify/ the /release/ to be of /Beta/
or /General Availability/ (/GA/) quality, as defined by the Apache HTTPD
project. Subsequent /votes/ may /reclassify/ the /release/, either to
promote it or to /demote/ it, as need be.
This may not be the way releases are handled now days.
Since the comitters are the ones who do the work, they make the
decisions, and reclassification would add more work.
It would give developers more justification to upgrade to a newer
version of Struts, since managers can grasp Beta vs GA.
On 3/13/2012 3:30 AM, Łukasz Lenart wrote:
2012/3/10 Robert<rlel...@apache.org>:
I was under the impression that any release past or present could be demoted
if deficiency were found.
Perhaps this has been done but may not be clear to a casual user. The page
http://struts.apache.org/downloads.html
does only list two releases. However, below that is the wording:
'As a courtesy, we retain archival copies of the website for each "General
Availability" release. Product support for older releases may be limited.'
As a casual user I might believe an older release is more "stable" and still
considered a GA release, when in fact there are deficiencies that should
rule it out of consideration.
It would see that possibly the sentence:
Product support for older releases may be limited.
Could be revised but several attempts to revise this to point out that older
release may have vulnerabilities or bugs either sounded too severe or too
mild.
Thoughts?
Hmm... I don't understand what you mean :-(
Do you want to completely remove the older versions from the download page ?
Regards