On 11 Mar 07, at 1:56 AM 11 Mar 07, TslH wrote:
Hi, (first of all, please forgive my low-level in english) I'm currently looking into the maven website. If I hadn't make mistake, there's no branches of the site for the different release. Isn't there a way to improve the website coherency?
Yes, I think by someone being accountable and the site undergoing release plans like all the other artifacts that we have.
Here an example: there's still some outdated information on the website, as in the download.apt file that talk about version 2.0.3 (not even the 2.0.4...), or there's the guide-building-m2.apt that required to set up a variable to maven-2.0.5 instead of 2.0.6 (I filled yesterday a doc-bug report MVN-2827 about it). In the same way, we can't anticipate the 2.0.6 release: there's not work-in-progress copy for the next release.
Wendy seems to have applied your patch and I just started trying to track project references and replacing them with a variable that can be interpolated. Until the site plugin works to interpolate project information this will do.
So, we have a mix of release 2.0.3, 2.0.4 and 2.0.5 in the website. That doesn't reflect the global professionalism of the maven development.
It's true, and it's a valid observation.
Can I suggest to apply the same kind of branches policy for maven website? And a last question: who is currently responsible for the maven website?
There is currently no one in that official capacity but I think it would be nice if people stepped up for short periods of time to manage releases and improvements to the site.
Jason.
Thanks, Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
