[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

2017-06-02 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-5019:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Issue resolved by pull request 3212
[https://github.com/apache/kafka/pull/3212]

> Exactly-once upgrade notes
> --
>
> Key: KAFKA-5019
> URL: https://issues.apache.org/jira/browse/KAFKA-5019
> Project: Kafka
>  Issue Type: Sub-task
>  Components: clients, core, producer 
>Reporter: Ismael Juma
>Assignee: Jason Gustafson
>Priority: Blocker
>  Labels: documentation, exactly-once
> Fix For: 0.11.0.0
>
>
> We have added some basic upgrade notes, but we need to flesh them out. We 
> should cover every item that has compatibility implications as well new and 
> updated protocol APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

2017-06-02 Thread Jason Gustafson (JIRA)

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

Jason Gustafson updated KAFKA-5019:
---
Status: Patch Available  (was: In Progress)

> Exactly-once upgrade notes
> --
>
> Key: KAFKA-5019
> URL: https://issues.apache.org/jira/browse/KAFKA-5019
> Project: Kafka
>  Issue Type: Sub-task
>  Components: clients, core, producer 
>Reporter: Ismael Juma
>Assignee: Jason Gustafson
>Priority: Blocker
>  Labels: documentation, exactly-once
> Fix For: 0.11.0.0
>
>
> We have added some basic upgrade notes, but we need to flesh them out. We 
> should cover every item that has compatibility implications as well new and 
> updated protocol APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

2017-05-23 Thread Apurva Mehta (JIRA)

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

Apurva Mehta updated KAFKA-5019:

Labels: documentation exactly-once  (was: exactly-once)

> Exactly-once upgrade notes
> --
>
> Key: KAFKA-5019
> URL: https://issues.apache.org/jira/browse/KAFKA-5019
> Project: Kafka
>  Issue Type: Sub-task
>  Components: clients, core, producer 
>Reporter: Ismael Juma
>Priority: Blocker
>  Labels: documentation, exactly-once
> Fix For: 0.11.0.0
>
>
> We have added some basic upgrade notes, but we need to flesh them out. We 
> should cover every item that has compatibility implications as well new and 
> updated protocol APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

2017-05-23 Thread Apurva Mehta (JIRA)

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

Apurva Mehta updated KAFKA-5019:

Labels: exactly-once  (was: )

> Exactly-once upgrade notes
> --
>
> Key: KAFKA-5019
> URL: https://issues.apache.org/jira/browse/KAFKA-5019
> Project: Kafka
>  Issue Type: Sub-task
>  Components: clients, core, producer 
>Reporter: Ismael Juma
>Priority: Blocker
>  Labels: exactly-once
> Fix For: 0.11.0.0
>
>
> We have added some basic upgrade notes, but we need to flesh them out. We 
> should cover every item that has compatibility implications as well new and 
> updated protocol APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

2017-05-18 Thread Apurva Mehta (JIRA)

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

Apurva Mehta updated KAFKA-5019:

Priority: Blocker  (was: Critical)

> Exactly-once upgrade notes
> --
>
> Key: KAFKA-5019
> URL: https://issues.apache.org/jira/browse/KAFKA-5019
> Project: Kafka
>  Issue Type: Sub-task
>  Components: clients, core, producer 
>Reporter: Ismael Juma
>Priority: Blocker
> Fix For: 0.11.0.0
>
>
> We have added some basic upgrade notes, but we need to flesh them out. We 
> should cover every item that has compatibility implications as well new and 
> updated protocol APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)