2012/3/20 Robert Leland <rlel...@apache.org>: > Its more on encouraging users to move to releases where bug fixes and > security vulnerability fixes have been made.
Ok, but still unclear for me :/ > 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. What do you propose ? Regards -- Łukasz http://www.lenart.org.pl/ mobile +48 606 323 122, office +27 11 0838747 Warszawa JUG conference - Confitura http://confitura.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
