You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Jan Høydahl (Jira)" <ji...@apache.org> on 2019/10/16 23:01:00 UTC
[jira] [Comment Edited] (LUCENE-8987) Move Lucene web site from svn
to git
[ https://issues.apache.org/jira/browse/LUCENE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953165#comment-16953165 ]
Jan Høydahl edited comment on LUCENE-8987 at 10/16/19 11:00 PM:
----------------------------------------------------------------
Steps
# Create new git repo '{{lucene-site'}}
# Create folder structure and copy old site (excluding JavaDoc and online RefGuide) from svn into appropriate folder(s)
# Adapt to make local Pelican site build work for building the barebones site, and commit to master branch
# Add {{.asf.yaml}} file with a 'staging' profile for branch asf-staging, and a 'publish' profile for branch 'asf-site', and a 'pelican' directive to auto build from 'master' branch and put site into 'asf-staging' branch (/output folder).
# Verify that the staging build kicks off and that a site appears in [lucene.staged.apache.org|https://lucene.staged.apache.org/] (note that this is different from lucene.staging.apache.org that old CMS uses)
# Find a solution for JavaDoc and RefGuide, which are *huge* amounts of statically generated HTML uploaded by RM during build.
** These should just be put on a filesystem somewhere, outside of git
** Do some {{.htaccess}} magic to make them appear in the right locations of the site
# Once the staging site is good, merge {{asf-staging}} into {{asf-site}} branch to publish. This will automatically disable CMS.
# Commit a README-NOT-IN-USE file to old svn repo and make it read-only
Note that also the RM guidelines need to be updated wrt
* how to update website, download pages etc during a release
* how to publish JavaDoc
* how to publish RefGuide HTML
was (Author: janhoy):
Steps
# Create new git repo '{{lucene-site'}}
# Create folder structure and copy old site from svn into appropriate folder(s)
# Adapt to make local Pelican site build work, and commit to master branch
# Add {{.asf.yaml}} file with a 'staging' profile for branch asf-staging, and a 'publish' profile for branch 'asf-site'
# Merge master branch into 'asf-staging' and verify that the staging build kicks off and that a site appears in [lucene.staged.apache.org|https://lucene.staged.apache.org/] (note that this is different from lucene.staging.apache.org that old CMS uses)
# Iterate until the site is perfect for publishing
# Merge master branch into 'asf-site' branch, which will publish to the real site and automatically disable old CMS
# Commit a README-NOT-IN-USE file to old svn repo and make it read-only
> Move Lucene web site from svn to git
> ------------------------------------
>
> Key: LUCENE-8987
> URL: https://issues.apache.org/jira/browse/LUCENE-8987
> Project: Lucene - Core
> Issue Type: Task
> Components: general/website
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Attachments: lucene-site-repo.png
>
>
> INFRA just enabled [a new way of configuring website build|https://s.apache.org/asfyaml] from a git branch, [see dev list email|https://lists.apache.org/thread.html/b6f7e40bece5e83e27072ecc634a7815980c90240bc0a2ccb417f1fd@%3Cdev.lucene.apache.org%3E]. It allows for automatic builds of both staging and production site, much like the old CMS. We can choose to auto publish the html content of an {{output/}} folder, or to have a bot build the site using [Pelican|https://github.com/getpelican/pelican] from a {{content/}} folder.
> The goal of this issue is to explore how this can be done for [http://lucene.apache.org|http://lucene.apache.org/] by, by creating a new git repo {{lucene-site}}, copy over the site from svn, see if it can be "Pelicanized" easily and then test staging. Benefits are that more people will be able to edit the web site and we can take PRs from the public (with GitHub preview of pages).
> Non-goals:
> * Create a new web site or a new graphic design
> * Change from Markdown to Asciidoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org