You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/05/24 05:41:47 UTC
[jira] [Created] (CASSANDRA-2695) Upgrade to Whirr 0.5.0
Upgrade to Whirr 0.5.0
----------------------
Key: CASSANDRA-2695
URL: https://issues.apache.org/jira/browse/CASSANDRA-2695
Project: Cassandra
Issue Type: Test
Components: Core
Reporter: Stu Hood
Assignee: Stu Hood
When Whirr 0.5.0 is released, we can take advantage of WHIRR-220 for tarball upload.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-2695) Upgrade to Whirr 0.5.0
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2695.
---------------------------------------
Resolution: Won't Fix
Assignee: (was: Stu Hood)
Sounds like consensus is we don't want to pursue the whirr-based dtests any farther.
> Upgrade to Whirr 0.5.0
> ----------------------
>
> Key: CASSANDRA-2695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2695
> Project: Cassandra
> Issue Type: Test
> Components: Core
> Reporter: Stu Hood
>
> When Whirr 0.5.0 is released, we can take advantage of WHIRR-220 for tarball upload.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira