[
https://issues.apache.org/jira/browse/SOLR-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777048#comment-13777048
]
Hoss Man commented on SOLR-5085:
--------------------------------
I've revised the process to take advantage of the dist/dev repo, and added some
scripts to make things easier – including naming files, sha1, pgp signing, and
generating the "svn mv" commands when it's time to publish...
https://cwiki.apache.org/confluence/pages/diffpages.action?pageId=33294406&originalId=34024365
https://cwiki.apache.org/confluence/display/solr/Internal+-+How+To+Publish+This+Documentation
I'll leave this bug open until Cassandra has a chance to try out the new
process & scripts doing the 4.5 ref guide release.
New Scripts...
https://svn.apache.org/r1526083
> update ref guide release process to account for SHA1 checksum, PGP signing,
> and KEYS files
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-5085
> URL: https://issues.apache.org/jira/browse/SOLR-5085
> Project: Solr
> Issue Type: Task
> Reporter: Hoss Man
> Assignee: Hoss Man
>
> https://cwiki.apache.org/confluence/display/solr/Internal+-+How+To+Publish+This+Documentation
> * section on generating the .pdf needs to also generate a .asc and .sha1
> ** ideally script this, borrow from buildAndPushRelease.py
> * make corresponding updates to the post-vote publish section
> ** might as well update process to take advantage of
> https://dist.apache.org/repos/dist/dev and using "svn mv" to publish
> ** https://www.apache.org/dev/release.html#upload-ci
> * need to figure out what KEYS files (if any) process should mention keeping
> up to date before PGP signing files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
