You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/11/10 18:55:13 UTC
[jira] Created: (WHIRR-140) include KEYS file in release artifact.
include KEYS file in release artifact.
--------------------------------------
Key: WHIRR-140
URL: https://issues.apache.org/jira/browse/WHIRR-140
Project: Whirr
Issue Type: Improvement
Components: build
Affects Versions: 0.2.0
Reporter: Patrick Hunt
Priority: Blocker
Fix For: 0.3.0
Via Chris Mattmann, from comment on incubator vote for release 0.2.0:
--
Minor nit: You didn't include the KEYS file in your src dist, so I had to go poking around your SVN to find it. Either include a link to the KEYS in your release VOTE email or please include it in your src distro (better!), or your RC staging dir (even better too!) :)
--
Sounds like we should update the release process to include it in both the src distro artifact and staging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WHIRR-140) include KEYS file in release artifact.
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White resolved WHIRR-140.
-----------------------------
Resolution: Fixed
I think this can be closed since a link to the KEYs file is now included in the RC email. Please re-open if you disagree.
> include KEYS file in release artifact.
> --------------------------------------
>
> Key: WHIRR-140
> URL: https://issues.apache.org/jira/browse/WHIRR-140
> Project: Whirr
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Priority: Blocker
> Fix For: 0.3.0
>
>
> Via Chris Mattmann, from comment on incubator vote for release 0.2.0:
> --
> Minor nit: You didn't include the KEYS file in your src dist, so I had to go poking around your SVN to find it. Either include a link to the KEYS in your release VOTE email or please include it in your src distro (better!), or your RC staging dir (even better too!) :)
> --
> Sounds like we should update the release process to include it in both the src distro artifact and staging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-140) include KEYS file in release
artifact.
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930689#action_12930689 ]
Patrick Hunt commented on WHIRR-140:
------------------------------------
I've updated the howtorelease page to remind release managers that their signing key should be included in the KEYS file. I also changed the voting/release email templates to include a link to the file.
https://cwiki.apache.org/confluence/display/WHIRR/How+To+Release
> include KEYS file in release artifact.
> --------------------------------------
>
> Key: WHIRR-140
> URL: https://issues.apache.org/jira/browse/WHIRR-140
> Project: Whirr
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Priority: Blocker
> Fix For: 0.3.0
>
>
> Via Chris Mattmann, from comment on incubator vote for release 0.2.0:
> --
> Minor nit: You didn't include the KEYS file in your src dist, so I had to go poking around your SVN to find it. Either include a link to the KEYS in your release VOTE email or please include it in your src distro (better!), or your RC staging dir (even better too!) :)
> --
> Sounds like we should update the release process to include it in both the src distro artifact and staging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.