You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/01/21 03:31:44 UTC

[jira] Resolved: (WHIRR-127) binary assembly from WHIRR-100 is not generated as part of release process

     [ https://issues.apache.org/jira/browse/WHIRR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White resolved WHIRR-127.
-----------------------------

    Resolution: Fixed
      Assignee: Tom White

I've updated the instructions with manual steps at https://cwiki.apache.org/confluence/display/WHIRR/How+To+Release. Longer term we should fix the pom so that this happens automatically. See WHIRR-213.

> binary assembly from WHIRR-100 is not generated as part of release process
> --------------------------------------------------------------------------
>
>                 Key: WHIRR-127
>                 URL: https://issues.apache.org/jira/browse/WHIRR-127
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.2.0
>            Reporter: Patrick Hunt
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.3.0
>
>
> As part of the release for 0.2.0 the assembly from WHIRR-100 is not generated (nor pushed to the public repos). This should be addressed for 0.3.0 (I did it manually for 0.2.0)
> I made a few notes on the whirr howtorelease page (todo). In particular how to generate the assembly (sign/md5/sha1), copy to the maven staging repo, also wget from staging to the ~<releasemanagerhome> directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.