2010/10/26 Stefano Bagnara <[email protected]>: > 2010/10/26 Eric Charles <[email protected]>: >> I would like to propose a new menu >> Sever 3.0 >> Server 2.3.2 >> Archive >> >> ... and move the Server 2.3.1, 2.3.0, 2.2.0 to the Archive page. >> >> The 2.3.2 would need to get regenerated and republished. > > +1, maybe "Server v3" and "Server v2" are more general for a menu name > that we have in every page, otherwise at every subrelease we have to > recreate the whole site, but take this only as an hint (you seems to > understand the implication so I'm fine your choices).
+1 to Stefano's suggestion > >> If ok with this, there is 3 actions: >> - Republish 2.3.2: I tried to build the site, but it fails to download the >> needed dependency. I will retry from another internet connection. > > ok. Maybe 2.3 needs maven 2 because maven 3 deprecated/removed some > stuff we used in 2.3 (local repository in the stage module and the > legacy repository style). > >> - In the index pages, push users to download and try 3.0-M1 rather than the >> stable 2.3.2. > > I would prefer to keep pushing users to 2.3.2 for a while. 3.0-M1 is > still too new to push it to everyday users. 2.3.2 instead is proven > stable. So, let's start linking 3.0 for early adopters and testers, > but don't "push" it too much before the GA release. +1 to Stefano's suggestion > >> - Automatically update the nightly dir. if needed, cause we already have two >> places to download the snapshots; hudson and maven snaphot repo. > > +1 +1 > > Stefano > Bye, Norman --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
