Kengo Seki created YETUS-409:
--------------------------------
Summary: Some fixes and improvements for "Cleanup" section in
"Managing a Release" document
Key: YETUS-409
URL: https://issues.apache.org/jira/browse/YETUS-409
Project: Yetus
Issue Type: Bug
Components: website and documentation
Affects Versions: 0.3.0
Reporter: Kengo Seki
Follow-up from 0.3.0 release.
h5. Item 2:
On my first try, {{git tag --sign}} failed as follows:
{code}
[sekikn@localhost yetus]$ git tag --sign rel/0.3.0
22ee2cf74c05055c58d47469012e1321276e1b1b
gpg: skipped "Kengo Seki <[email protected]>": No secret key
gpg: signing failed: No secret key
error: gpg failed to sign the data
error: unable to sign the tag
The tag message has been left in .git/TAG_EDITMSG
{code}
That was because I forgot {{git config --global user.signingkey}}. It would be
helpful if there is a note about it.
h5. Item 3:
This command
{code}
$ cp path/to/yetus-dist-dev/0.2.0-RC1 0.2.0
{code}
fails, because the source is a directory.
But {{cp -r}} isn't also preferred, because it copies unnecessary .svn
directory.
So I did:
{code}
$ mkdir 0.3.0
$ cp ~/yetus-dist-dev/0.3.0-RC1/* 0.3.0
{code}
h5. Item 9:
{code}
YETUS-XXX. add release 0.1.0.
{code}
s/0.1.0/0.2.0/.
h5. Item 12:
link to YETUS-316 is broken.
h5. Item 13:
The announce email should contain the URL for the release notes as well as the
change list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
