You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/11/24 02:26:39 UTC

[jira] Created: (CASSANDRA-577) document upgrade process from 0.4 to 0.5

document upgrade process from 0.4 to 0.5
----------------------------------------

                 Key: CASSANDRA-577
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-577
             Project: Cassandra
          Issue Type: Task
          Components: Core
            Reporter: Jonathan Ellis
            Assignee: Jonathan Ellis
            Priority: Minor
             Fix For: 0.5


(should this go in README or a separate UPGRADING file?)

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


[jira] Commented: (CASSANDRA-577) document upgrade process from 0.4 to 0.5

Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787153#action_12787153 ] 

Eric Evans commented on CASSANDRA-577:
--------------------------------------

Looks good; I can't think of anything else to include. +1

> document upgrade process from 0.4 to 0.5
> ----------------------------------------
>
>                 Key: CASSANDRA-577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-577
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 577.patch
>
>
> (should this go in README or a separate UPGRADING file?)

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


[jira] Commented: (CASSANDRA-577) document upgrade process from 0.4 to 0.5

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

Jonathan Ellis commented on CASSANDRA-577:
------------------------------------------

Do we need anything here besides the commitlog format change business?

> document upgrade process from 0.4 to 0.5
> ----------------------------------------
>
>                 Key: CASSANDRA-577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-577
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>
> (should this go in README or a separate UPGRADING file?)

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


[jira] Updated: (CASSANDRA-577) document upgrade process from 0.4 to 0.5

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

Jonathan Ellis updated CASSANDRA-577:
-------------------------------------

    Attachment: 577.patch

> document upgrade process from 0.4 to 0.5
> ----------------------------------------
>
>                 Key: CASSANDRA-577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-577
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 577.patch
>
>
> (should this go in README or a separate UPGRADING file?)

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


[jira] Commented: (CASSANDRA-577) document upgrade process from 0.4 to 0.5

Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782012#action_12782012 ] 

Eric Evans commented on CASSANDRA-577:
--------------------------------------

We should probably start creating release notes which unlike a changelog only documents the changes expected to be operational relevant, in greater detail/plainer language, including any pre/post upgrade procedures.

> document upgrade process from 0.4 to 0.5
> ----------------------------------------
>
>                 Key: CASSANDRA-577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-577
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>
> (should this go in README or a separate UPGRADING file?)

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


[jira] Commented: (CASSANDRA-577) document upgrade process from 0.4 to 0.5

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

Hudson commented on CASSANDRA-577:
----------------------------------

Integrated in Cassandra #282 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/282/])
    

> document upgrade process from 0.4 to 0.5
> ----------------------------------------
>
>                 Key: CASSANDRA-577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-577
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 577.patch
>
>
> (should this go in README or a separate UPGRADING file?)

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