[
https://issues.apache.org/jira/browse/SOLR-17250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841546#comment-17841546
]
Gus Heck commented on SOLR-17250:
---------------------------------
And hit it again here:
{code:java}
>> 6
We need to update the website so that the download pages list the new release,
and the
"latest" javadoc links point to the new release.Fortunately the only thing you
need to change is a few variables in `pelicanconf.py`.
If you release a current latest release, change the `SOLR_LATEST_RELEASE` and
`SOLR_LATEST_RELEASE_DATE`
variables.
If you relese a bugfix release for previous version, then change the
`SOLR_PREVIOUS_MAJOR_RELEASE` variable.
Edit pelicanconf.py to update version numbers cd
~/.solr-releases/9.6.0/solr-site
# Edit the pelicanconf.file
/usr/bin/nano pelicanconf.py
git commit -am "Update version variables for release 9.6.0"
{code}
(previous step checked out a new copy of the website repo)
> Release wizard needs to set user/email for repo it checks out
> -------------------------------------------------------------
>
> Key: SOLR-17250
> URL: https://issues.apache.org/jira/browse/SOLR-17250
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: release-scripts
> Reporter: Gus Heck
> Priority: Major
>
> The script seems to assume you will have a global user/email set but for
> folks with many clients, and or are active on other (non Apache) open source
> projects this is often unwise.
> The script should ask user/email and set them locally on the working copy it
> checks out
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
