You’re right, Konstantin. I’ve created a JIRA issue: <https://issues.apache.org/jira/browse/SOLR-7763>
Steve But for some > On Jul 7, 2015, at 12:20 PM, Konstantin Gribov <[email protected]> wrote: > > Currently API docs for Lucene can be found in 2 clicks from lucene.apache.org > ("lucene core" link, then 5.2.1 in "release docs"). > > But it isn't so easy for Solr. I haven't found it on lucene.apache.org/solr/ > site anywhere (maybe it can be found somewhere in cwiki, but not on front > page of reference guide there). Only google helped me with it. > > It seems to be more important issue for current site than redirect to 5.2.0 =) > > I think, link to lucene.apache.org/solr/api/ should be added to > resources/docs on Solr site. > > вт, 7 июля 2015 г. в 17:42, Shawn Heisey <[email protected]>: > On 7/6/2015 5:35 PM, Konstantin Gribov wrote: > > Yes, version-agnostic URL is much better. I haven't found it since > > I've found only direct links to solr javadoc for earlier versions. I > > will update it now. > > The API for 5.2.0 should be identical to 5.2.1. We try extremely hard > to NOT change the API on a bugfix release, so that users can upgrade and > get critical fixes without changing their code or their configs. > > The only time I think a version number should be used in a javadoc URL > is if the surrounding text is pointing something out that is > version-specific. > > One of the tasks I've read about at release time is to adjust all > public-facing generic URLs to point to the newly released version. I > don't know if it's normal to skip this for a bugfix release or not ... > because API breaks are pretty much never done on a bugfix release, it > probably isn't critical to update the javadoc redirect. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- > Best regards, > Konstantin Gribov --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
