You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Johan Oskarsson (JIRA)" <ji...@apache.org> on 2009/05/28 19:09:45 UTC

[jira] Created: (CASSANDRA-203) Change versions in jira

Change versions in jira
-----------------------

                 Key: CASSANDRA-203
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-203
             Project: Cassandra
          Issue Type: Task
            Reporter: Johan Oskarsson


As per mailing list discussions, 0.3 and 0.4 becomes 0.3.0 and 0.4.0

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


[jira] Commented: (CASSANDRA-203) Change versions in jira

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721374#action_12721374 ] 

Johan Oskarsson commented on CASSANDRA-203:
-------------------------------------------

Then how would you know if a bug assigned to 0.3 was fixed in 0.3.0 or 0.3.1?

> Change versions in jira
> -----------------------
>
>                 Key: CASSANDRA-203
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-203
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> As per mailing list discussions, 0.3 and 0.4 becomes 0.3.0 and 0.4.0

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


[jira] Commented: (CASSANDRA-203) Change versions in jira

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721376#action_12721376 ] 

Jonathan Ellis commented on CASSANDRA-203:
------------------------------------------

it's fixed in the release after it's committed.

> Change versions in jira
> -----------------------
>
>                 Key: CASSANDRA-203
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-203
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> As per mailing list discussions, 0.3 and 0.4 becomes 0.3.0 and 0.4.0

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


[jira] Commented: (CASSANDRA-203) Change versions in jira

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721719#action_12721719 ] 

Johan Oskarsson commented on CASSANDRA-203:
-------------------------------------------

Doesn't that make it harder then necessary for users to find the version that has fixed the bug they've stumbled upon?

I always look at the Hadoop JIRA page for point releases to know if it is worth upgrading or not, if it contains fixes for bugs we might run the risk of encountering. It wouldn't be any noticeable increase in workload to assign to 0.3.0 instead of 0.3. 

> Change versions in jira
> -----------------------
>
>                 Key: CASSANDRA-203
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-203
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> As per mailing list discussions, 0.3 and 0.4 becomes 0.3.0 and 0.4.0

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


[jira] Resolved: (CASSANDRA-203) Change versions in jira

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-203.
--------------------------------------

    Resolution: Won't Fix

0.3 can refer to 0.3.0, 0.3.1, etc.  it's fine the way it is.

> Change versions in jira
> -----------------------
>
>                 Key: CASSANDRA-203
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-203
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> As per mailing list discussions, 0.3 and 0.4 becomes 0.3.0 and 0.4.0

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