: thats the whole problem with /api: its not defined at all. it has bee nvery clearly defined since it was created: "the latest javadocs" ... just because we no longer explicitly link to it, doesn't mean we should stop trying to live up to the point of the link -- especially not when it's so fucking easy to do.
: having shit like this just turns into 'lets blame the release manager : when things change and its not the way i want'. where do you get that anyone is going to blame release managers for something? having this redirect isn't going to break anything, nor does it have anything to do with anything an RM should give a fuck about. the only reason we had a hicup with it on tuesday was because that was the day we made the change from only hosting single copy of the solr javadocs, re-using a single path for each new version, to having multiple versions with distinct pathes -- and when we made that change we did *NOT* have any redirect like this in place at all. that change could have been made at any time, regardless of wether it involved a new release, regardless of wether it was done by an RM, and the problem would have been the same: the missing redirect ment old links broke. that was a one time change, that will never affect any other release in the future ever again: we just keep adding new directories for the new docs. having this redirect doesn't affect that in any way shape or form : same goes for download redirect links (I will open an issue tomorrow: : either we remove these download redirect llinks completely, or we fix : them to take versions, because having to add ?'s with bogus stuff on I already opened an issue for that when we noticed this during 3.6 .. no one who cares about the google analytics and understands javascript has bothered to pick it up... https://issues.apache.org/jira/browse/LUCENE-3978 -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
