cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Oskarsson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-203) Change versions in jira
Date Fri, 19 Jun 2009 10:01:07 GMT

    [ 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.


Mime
View raw message