[
https://issues.apache.org/jira/browse/YETUS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166770#comment-15166770
]
Sean Busbey commented on YETUS-226:
-----------------------------------
{quote}
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.
{quote}
good catch.
{quote}
On the version date:
bq. set the release date to when you expect your next vote thread to close.
This date will be used by our generated release notes.
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?
{quote}
At least in our current case, where the release notes are getting put together
as a part of the RC process, it doesn't work since the notes are being
generated before the date of the release. Technically the release date is when
the vote passes, which has to be at least 72 hours after the candidate is
proposed.
{quote}
Should this have a --use-agent flag in there?
{code}gpg --armor --output "${artifact}".asc --detach-sig
"${artifact}"}{code}
{quote}
If you think it will help, but I don't know if any of the current guides talk
about gpg agent. I just enter my password a few times. :)
{quote}
Awkward:
bq. Update update master for release. You should update the docs in master for
the new release.
{quote}
Wow. I must have been tired.
{quote}
Mark this as To Be Documented?
bq. Publish convenience artifacts (maven, homebrew, etc).
{quote}
Sure. Or I could just leave it out until we do it. :)
> 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)
