[
https://issues.apache.org/jira/browse/YETUS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166623#comment-15166623
]
Allen Wittenauer commented on YETUS-226:
----------------------------------------
I ran through as many of the instructions as I could. Hopefully I didn't skip
any. ;) In any case, these are the things I noticed.
* On the key signing part:
{code}
$ svn co https://dist.apache.org/repos/dist/release/yetus yetus-dist-release
$ (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
{code}
It'd probably be good to replace "your name" with "your PGP name" or whatever
so that people know you're referencing the name in the key list. Also, missing
a cd or a path to the KEYS directory is needed here so that it actually updates
the KEYS file.
* On the version date:
{code}
set the release date to when you expect your next vote thread to close. This
date will be used by our generated release notes.
{code}
The intention was always that --usetoday could be used to set the actual date
in the release artifact without having to set it in JIRA. Is this actually not
feasible?
* Should this have a --use-agent flag in there?
{code}
gpg --armor --output "${artifact}".asc --detach-sig "${artifact}"
{code}
* Awkward:
{code}
Update update master for release. You should update the docs in master for the
new release.
{code}
* Mark this as To Be Documented?
{code}
Publish convenience artifacts (maven, homebrew, etc).
{code}
> Document release process
> ------------------------
>
> Key: YETUS-226
> URL: https://issues.apache.org/jira/browse/YETUS-226
> Project: Yetus
> Issue Type: Improvement
> Components: website and documentation
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: 0.2.0
>
> Attachments: YETUS-226.1.patch, YETUS-226.2.patch, YETUS-226.3.patch,
> YETUS-226.4.patch
>
>
> document how to handle making a release candidate and call a vote.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
