[ http://issues.apache.org/jira/browse/LUCENE-708?page=comments#action_12454463 ] Hoss Man commented on LUCENE-708: ---------------------------------
maybe there is some confusion as to the purpose of this issue ... i was under the impression that Grant's primary goal was to make it possible for the site to host nightly builds of the *documentation* ... ie: the "static" docs (like features.html, fileformats.html and gettingstarted.html) and the "dynamic" javadocs ... so that it was possible to easily access this information for the "trunk" seperate and distinctly from the previous versions of hte same information included with the most recent release(s). This biggest question seems to be what is the "default" ... as we've already seen with the current site, it's very hard to have the "main" versions of the site pages allways reflect the last stable release, because some of htep ages (news, whoweare, etc...) need to rev more frequently then that. As i suggested in email, i think the "default" URLs for various docs, ie... http://lucene.apache.org/java/docs/api/ http://lucene.apache.org/java/docs/gettingstarted.html http://lucene.apache.org/java/docs/fileformats.html ...should reflect the most current version of hte information available, presumably generated as part of the nightly build process (that way the javadocs which might link to the static files or vice-versa are allways in sync) Documentation for recent releases (regardless of whether they are the most recent or not) should be available using URLs with the release number in them... http://lucene.apache.org/java/2.0-docs/api/ http://lucene.apache.org/java/2.0-docs/gettingstarted.html http://lucene.apache.org/java/2.0-docs/fileformats.html Using the "Site Versions" left nav element to link to the various versions... Nightly -> "./" Stable (2.0) -> "../2.0-docs/" 1.9.1 -> "../1.9.1-docs" 1.9 -> "../1.9-docs" 1.4.3 -> "../14.3-docs" ...people have expressed skepticism at the idea that the "default" site documentation would be for the trunk instead of the last stable release, but that seems like the simplest most straight forward way for things to work. People lookingfor information about a specific release have it readily available 9and unlike in the past: it will be available at a URL that will never change on them) > Setup nightly build website links and docs > ------------------------------------------ > > Key: LUCENE-708 > URL: http://issues.apache.org/jira/browse/LUCENE-708 > Project: Lucene - Java > Issue Type: Improvement > Components: Website > Reporter: Grant Ingersoll > Assigned To: Grant Ingersoll > Priority: Minor > > Per discussion on mailing list, we are going to setup a Nightly Build link on > the website linking to the docs (and javadocs) generated by the nightly build > process. The build process may need to be modified to complete this task. > Going forward, the main website will, for the most part, only be updated per > releases (I imagine exceptions will be made for News items and per > committer's discretion). The Javadocs linked to from the main website will > always be for the latest release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
