[
https://issues.apache.org/jira/browse/LUCENE-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-9034.
-----------------------------------
Resolution: Fixed
The new site is now live:
- https://lucene.apache.org/ (we should maybe just fix certificate warnings
because of unencrypted content still there)
- The Subversion Git CMS tree was cleaned up (added file "MOVED_TO_GIT")
- The Subversion folder with the Javadocs and Refguide was kept alive:
https://svn.apache.org/repos/infra/websites/production/lucene/content
To publish Javadocs and Refguide nothing has changed, only extpath.txt is gone.
Just commit to subversion as you did before.
> Officially publish the new site
> -------------------------------
>
> Key: LUCENE-9034
> URL: https://issues.apache.org/jira/browse/LUCENE-9034
> Project: Lucene - Core
> Issue Type: Sub-task
> Components: general/website
> Reporter: Jan Høydahl
> Assignee: Uwe Schindler
> Priority: Major
>
> Publishing the web site means creating a publish branch and adding the right
> magic instructions to {{.asf.yml}} etc. This will then publish the new site
> and disable old CMS.
> Before we do that we should
> # Make sure all docs and release tools are updated for new site publishing
> instructions
> # Create a PR with latest changes in old CMS site since the export. This
> will be the changes done during 8.3.0 release and possibly some news entries
> related to security issues etc.
> After publishing we should ask INFRA to make old site svn read-only (and
> perhaps do a commit that replaces svn content with a README.txt), so it is
> obvious for everyone that we have migrated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
