Here’s a simple example of the problem: A user links to the current doc for the PositionFilter. That link should continue to work for years to come – if it is a versioned link. But if it links to a non-versioned doc page, and in 4.4 PositionFilter is removed, then suddenly the user’s link breaks. Or, ditto for a link from one of the Solr wiki pages.
-- Jack Krupansky From: Jan Høydahl Sent: Wednesday, May 22, 2013 6:14 PM To: [email protected] Subject: Re: ReleaseTodo update There was extension discussion about this previously on the mailing list. I found this, where in fact you are the one proposing the redirect to latest doc: http://search-lucene.com/m/HPcIC1Nx9NE1 If broken links are our main concern, perhaps we should deploy a BOT checking our CMS/Wiki nightly for broken links and email the dev list if found? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 22. mai 2013 kl. 23:07 skrev Robert Muir <[email protected]>: I would rather remove the redirect. if we want to have a redirect to a specific index.html thats way different than a rewrite rule that is ripe for abuse. There was extension discussion about this previously on the mailing list. On Wed, May 22, 2013 at 2:03 PM, Jan Høydahl <[email protected]> wrote: Sure, broken links may be and probably have already been an issue. Anyway, the goal of this doc change was to have consistency between the real world and the release todo, not to get stale redirects to some random version. You can always open a JIRA to propose changing all of this. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 22. mai 2013 kl. 19:24 skrev Robert Muir <[email protected]>: There was a lot of discussions about these links before. I don't think we should have such links. They just encourage broken links from the wiki etc. i don't want to see links like http://lucene.apache.org/core/api/core/org/apache/lucene/index/FieldInvertState.html going to http://lucene.apache.org/core/4_3_0/core/org/apache/lucene/index/FieldInvertState.html. These will only break as APIs evolve. Its better to have the version explicit. On Wed, May 22, 2013 at 6:39 AM, Jan Høydahl <[email protected]> wrote: WIKI updated, please review: https://wiki.apache.org/lucene-java/ReleaseTodo#Update_redirect_to_latest_Javadoc Also added redirects to the Lucene javadocs so that http://lucene.apache.org/core/api/ ... now works. If that was avoided on purpose for some reason, let me know and I'll remove it again. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 13. mai 2013 kl. 21:20 skrev Steve Rowe <[email protected]>: > Good catch, Jan - feel free to add this to the ReleaseTodo wiki page yourself. - Steve > > On May 12, 2013, at 7:18 PM, Jan Høydahl <[email protected]> wrote: > >> Hi, >> >> I discovered that the "doc" redirect still redirects to 4_1_0 javadocs. >> I changed .htaccess so it now points to 4_3_0 >> https://svn.apache.org/repos/asf/lucene/cms/trunk/content/.htaccess >> >> The Release TODO should mention updating this link - http://wiki.apache.org/lucene-java/ReleaseTodo >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> >> --------------------------------------------------------------------- >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
