On 3 January 2014 13:12, Benedikt Ritter <brit...@apache.org> wrote: > 2014/1/3 Henri Yandell <flame...@gmail.com> > >> Yes we change the site between releases. >> >> The bigger question is why we have a version number on the website, it >> isn't versioned. >> > > Well at least the repots have kind of a version, because they reflect the > state of the code they were build against. > And to me the reports for the latest release are far more important then > those for the current trunk.
+1 It's very useful having the Java Xref and Javadoc online for the current released version. For one thing, it makes it easier to deal with stacktraces in bug reports.. I've said it before - the main website should be about the code that has been voted on and released. Not whatever happens to be the current development state. > >> >> Hen >> >> >> On Thu, Jan 2, 2014 at 6:45 AM, Duncan Jones <dun...@wortharead.com> >> wrote: >> >> > Hi all, >> > >> > The top of the commons-lang web page reads: >> > >> > "Last Published: 01 January 2014 | Version: 3.3-SNAPSHOT " >> > >> > Shouldn't that read: >> > >> > "Last Published: 01 January 2014 | Version: 3.2 " ?? >> > >> > Or are we changing the site between releases, thus necessitating that >> > we build a site using the current (snapshot) version number? >> > >> > Thanks, >> > >> > Duncan >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
