[jira] [Commented] (LUCENE-9034) Officially publish the new site

["Jan Høydahl (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974664#comment-16974664 ] 

Jan Høydahl commented on LUCENE-9034:
-------------------------------------

This is necessary as the final step to actually replace the current website with the new from {{asf-site}} branch:
{code:sh}
# asf-site branch
git fetch && git checkout asf-site
cat << EOF > .asf.yaml
publish:
  whoami: asf-site
EOF
git add .asf.yaml
git commit -m "Auto publish live public website"
git push origin{code}

> 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
>            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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org