I just repeat myself: I would make a perm redirect (301) from api/ -> api3/. api3/ -> api-3.6.0 would be a 302 redirect, as it is official.
By this browsers will update their bookmarks and google bot will forget about the dying api/, too (with 301 redirect). Api3 is then official link to the actual api of version 3, api4 of version 4, pointing to current alpha (via 302 redirect). ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Robert Muir [mailto:rcm...@gmail.com] > Sent: Wednesday, July 04, 2012 7:35 PM > To: dev@lucene.apache.org > Subject: Re: Solr 3.6.0 javadocs are missing from the site > > On Wed, Jul 4, 2012 at 1:28 PM, Chris Hostetter <hossman_luc...@fucit.org> > wrote: > > > > : that's not what I mean. api/ should die. but I'm ok with api-3 that > > points > > > > Well then you and i have radically differnet opinions about SEO and > > good long term URL practices. > > clearly we do: i care about documentation not having broken links. > > but linking to api/ is fucked up. Those links *will break* when the api > changes. > > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional > commands, e-mail: dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
