You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ct...@apache.org on 2017/04/26 19:14:10 UTC
lucene-solr:jira/solr-10290: SOLR-10295: strawman process for
publishing HTML version
Repository: lucene-solr
Updated Branches:
refs/heads/jira/solr-10290 73148be0b -> 81c8215ce
SOLR-10295: strawman process for publishing HTML version
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/81c8215c
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/81c8215c
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/81c8215c
Branch: refs/heads/jira/solr-10290
Commit: 81c8215ce5dad3d5f06ad07fa9314133b9d0a542
Parents: 73148be
Author: Cassandra Targett <ct...@apache.org>
Authored: Wed Apr 26 14:13:45 2017 -0500
Committer: Cassandra Targett <ct...@apache.org>
Committed: Wed Apr 26 14:13:45 2017 -0500
----------------------------------------------------------------------
solr/solr-ref-guide/meta-docs/publish.adoc | 34 +++++++++++++++++++++++++
1 file changed, 34 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/81c8215c/solr/solr-ref-guide/meta-docs/publish.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/meta-docs/publish.adoc b/solr/solr-ref-guide/meta-docs/publish.adoc
new file mode 100644
index 0000000..f01978d
--- /dev/null
+++ b/solr/solr-ref-guide/meta-docs/publish.adoc
@@ -0,0 +1,34 @@
+= Publishing Process
+
+// A lot of this was copied from https://wiki.apache.org/lucene-java/ReleaseTodo#Website_.2B-.3D_javadocs. See that section for explanations for why some steps are required.
+
+== Publishing HTML Version
+
+=== Update extpaths.txt
+
+. Checkout CMS trunk: `svn co --depth=immediates https://svn.apache.org/repos/asf/lucene/cms/trunk/content website-source` ('content' is a very generic name. So, we check it out to a self-explanatory name such as 'website-source')
+. `cd website-source`
+. Add Guide branch dir: `echo solr/guide/X_Y_Z >> extpaths.txt`
+. Commit changes `svn commit -m "Update CMS production sync exceptions for X_Y_Z Guide" extpaths.txt`
+// Do we need to do this? copied from ReleaseTodo
+. Optionally, you can then delete the CMS checkout:
+[source]
+cd ..
+rm -rf website-source
+
+
+=== Push Guide to CMS Production
+
+Go to the checkout directory where you have built the Guide and push the documentation via subversion import. Example:
+`svn -m "Add Ref Guide for Solr 6.5" import <checkoutroot>/solr/build/solr-ref-guide/html-site https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/guide/6_5`
+
+Confirm you can browse to these URLs manually, and especially that solr javadocs link back to lucene's correctly. Example:
+https://lucene.apache.org/solr/guide/6_5
+
+=== Update Ref Guide Landing Page
+
+Update the landing page at https://lucene.apache.org/solr/guide to link to the newest version.
+
+// TODO:
+// - figure out process for updating guide
+// - decide if an automatic redirect is required