Steve Rowe commented on SOLR-6871:

Thanks [~janhoy] - for some reason your branch_6x commit didn't get posted here 
- from the email notification to commits@l.a.o:

Repository: lucene-solr
Updated Branches:
 refs/heads/branch_6x 082f8e3f9 -> 9611478c7

SOLR-6871: Fix precommit - accept /solr/downloads.html as valid link

(cherry picked from commit d146354)

Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/9611478c
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/9611478c
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/9611478c

Branch: refs/heads/branch_6x
Commit: 9611478c7e249b7c65d3807e2ae672aabaefa50b
Parents: 082f8e3
Author: Jan Høydahl <jan...@apache.org>
Authored: Thu Sep 22 10:52:01 2016 +0200
Committer: Jan Høydahl <jan...@apache.org>
Committed: Thu Sep 22 10:53:21 2016 +0200

> Need a process for updating & maintaining the new quickstart tutorial (and 
> any other tutorials added to the website)
> --------------------------------------------------------------------------------------------------------------------
>                 Key: SOLR-6871
>                 URL: https://issues.apache.org/jira/browse/SOLR-6871
>             Project: Solr
>          Issue Type: Task
>            Reporter: Hoss Man
>            Assignee: Steve Rowe
>            Priority: Minor
>         Attachments: SOLR-6871.patch
> Prior to SOLR-6058 the /solr/tutorial.html link on the website contained only 
> a simple landing page that then linked people to the "versioned" tutorial for 
> the most recent release -- or more specificly: the most recent release*s* 
> (plural) when we were releasing off of multiple branches (ie: links to both 
> the 4.0.0 tutorial, as well as the 3.6.3 tutorial when 4.0 came out)
> The old tutorial content lived along side the solr code, and was 
> automatically branched, tagged & released along with Solr.  When committing 
> any changes to Solr code (or post.jar code, or the sample data, or the sample 
> configs, etc..) you could also commit changes to the tutorial at th same time 
> and be confident that it was clear what version of solr that tutorial went 
> along with.
> As part of SOLR-6058, it seems that there was a concensus to move to a 
> keeping "tutorial" content on the website, where it can be integrated 
> directly in with other site content/navigation, and use the same look and 
> feel.
> I have no objection to this in principle -- but as a result of this choice, 
> there are outstanding issues regarding how devs should go about maintaining 
> this doc as changes are made to solr & the solr examples used in the tutorial.
> We need a clear process for where/how to edit the tutorial(s) as new versions 
> of solr come out and cahnges are made that mandate corisponding hanges to the 
> tutorial.  this process _should_ also account for things like having multiple 
> versions of the tutorial live at one time (ie: at some point in the future, 
> we'll certainly need to host the "5.13" tutorial if that's the current 
> "stable" release, but we'll also want to host the tutorial for "6.0-BETA" so 
> that people can try it out)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to