You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Ismael Juma <is...@juma.me.uk> on 2017/05/05 03:28:41 UTC
0.11.0.0 Release Update
Hi all,
We're quickly approaching our next time-based release. If you missed any of
the updates on the new time-based releases we'll be following, see
https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
for an explanation.
The release plan can be found in the usual location:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0
Here are the important dates (also documented in the wiki):
- KIP Freeze: May 10, 2017 (a KIP must be accepted by this date in order
to be considered for this release)
- Feature Freeze: May 17, 2017 (major features merged & working on
stabilization, minor features have PR, release branch cut; anything not in
this state will be automatically moved to the next release in JIRA)
- Code Freeze: May 31, 2017 (first RC created now)
- Release: June 14, 2017
There are a couple of changes based on Ewen's feedback as release manager
for 0.10.2.0:
1. We now have a KIP freeze one week before the feature freeze to avoid
the risky and confusing situation where some KIPs are being discussed,
voted on and merged all in the same week.
2. All the dates were moved from Friday to Wednesday so that release
management doesn't spill over to the weekend.
KIPs: we have 24 adopted with 10 already committed and 10 with patches in
flight. The feature freeze is 12 days away so we have a lot of reviewing to
do, but significant changes have been merged already.
Open JIRAs: As usual, we have a lot!
*https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC>*
146 at the moment. As we get nearer to the feature freeze, I will start
moving JIRAs out of this release.
* Closed JIRAs: So far ~191 closed tickets for 0.11.0.0:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC
* Release features:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 has
a "Release Features" section that will be included with the release
notes/email for the release. I added some items to get it going. Please add
to
this list anything you think is worth noting.
I'll plan to give another update next week just before the KIP freeze.
Ismael
Re: 0.11.0.0 Release Update
Posted by Ismael Juma <is...@juma.me.uk>.
Hi Michal,
We would like to allow for at least one stabilisation cycle after
exactly-once lands before we consider the 1.0 release. Soon after the
0.11.0.0 release, a release manager for the subsequent release will
hopefully volunteer and we can then discuss the details.
While on the subject, I will send an update on 0.11.0.0 later today or
tomorrow.
Ismael
On Fri, Jun 2, 2017 at 5:10 PM, Michal Borowiecki <
michal.borowiecki@openbet.com> wrote:
> Hi all,
>
> So will Exactly Once Semantics be reason enough to bump version to 1.0? Or
> is the leading zero here to stay indefinitely? :-)
>
> Cheers,
>
> Michal
>
> On 05/05/17 04:28, Ismael Juma wrote:
>
> Hi all,
>
> We're quickly approaching our next time-based release. If you missed any of
> the updates on the new time-based releases we'll be following, seehttps://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> for an explanation.
>
> The release plan can be found in the usual location:https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0
>
> Here are the important dates (also documented in the wiki):
>
> - KIP Freeze: May 10, 2017 (a KIP must be accepted by this date in order
> to be considered for this release)
> - Feature Freeze: May 17, 2017 (major features merged & working on
> stabilization, minor features have PR, release branch cut; anything not in
> this state will be automatically moved to the next release in JIRA)
> - Code Freeze: May 31, 2017 (first RC created now)
> - Release: June 14, 2017
>
> There are a couple of changes based on Ewen's feedback as release manager
> for 0.10.2.0:
>
> 1. We now have a KIP freeze one week before the feature freeze to avoid
> the risky and confusing situation where some KIPs are being discussed,
> voted on and merged all in the same week.
> 2. All the dates were moved from Friday to Wednesday so that release
> management doesn't spill over to the weekend.
>
> KIPs: we have 24 adopted with 10 already committed and 10 with patches in
> flight. The feature freeze is 12 days away so we have a lot of reviewing to
> do, but significant changes have been merged already.
>
> Open JIRAs: As usual, we have a lot!
>
> *https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC<https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC>*
>
> 146 at the moment. As we get nearer to the feature freeze, I will start
> moving JIRAs out of this release.
>
> * Closed JIRAs: So far ~191 closed tickets for 0.11.0.0:https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC
>
> * Release features:https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 has
> a "Release Features" section that will be included with the release
> notes/email for the release. I added some items to get it going. Please add
> to
> this list anything you think is worth noting.
>
> I'll plan to give another update next week just before the KIP freeze.
>
> Ismael
>
>
>
> --
> <http://www.openbet.com/> Michal Borowiecki
> Senior Software Engineer L4
> T: +44 208 742 1600 <020%208742%201600>
>
>
> +44 203 249 8448 <020%203249%208448>
>
>
>
> E: michal.borowiecki@openbet.com
> W: www.openbet.com
> OpenBet Ltd
>
> Chiswick Park Building 9
>
> 566 Chiswick High Rd
>
> London
>
> W4 5XT
>
> UK
> <https://www.openbet.com/email_promo>
> This message is confidential and intended only for the addressee. If you
> have received this message in error, please immediately notify the
> postmaster@openbet.com and delete it from your system as well as any
> copies. The content of e-mails as well as traffic data may be monitored by
> OpenBet for employment and security purposes. To protect the environment
> please do not print this e-mail unless necessary. OpenBet Ltd. Registered
> Office: Chiswick Park Building 9, 566 Chiswick High Road, London, W4 5XT,
> United Kingdom. A company registered in England and Wales. Registered no.
> 3134634. VAT no. GB927523612
>
Re: 0.11.0.0 Release Update
Posted by Michal Borowiecki <mi...@openbet.com>.
Hi all,
So will Exactly Once Semantics be reason enough to bump version to 1.0?
Or is the leading zero here to stay indefinitely? :-)
Cheers,
Michal
On 05/05/17 04:28, Ismael Juma wrote:
> Hi all,
>
> We're quickly approaching our next time-based release. If you missed any of
> the updates on the new time-based releases we'll be following, see
> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> for an explanation.
>
> The release plan can be found in the usual location:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0
>
> Here are the important dates (also documented in the wiki):
>
> - KIP Freeze: May 10, 2017 (a KIP must be accepted by this date in order
> to be considered for this release)
> - Feature Freeze: May 17, 2017 (major features merged & working on
> stabilization, minor features have PR, release branch cut; anything not in
> this state will be automatically moved to the next release in JIRA)
> - Code Freeze: May 31, 2017 (first RC created now)
> - Release: June 14, 2017
>
> There are a couple of changes based on Ewen's feedback as release manager
> for 0.10.2.0:
>
> 1. We now have a KIP freeze one week before the feature freeze to avoid
> the risky and confusing situation where some KIPs are being discussed,
> voted on and merged all in the same week.
> 2. All the dates were moved from Friday to Wednesday so that release
> management doesn't spill over to the weekend.
>
> KIPs: we have 24 adopted with 10 already committed and 10 with patches in
> flight. The feature freeze is 12 days away so we have a lot of reviewing to
> do, but significant changes have been merged already.
>
> Open JIRAs: As usual, we have a lot!
>
> *https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC>*
>
> 146 at the moment. As we get nearer to the feature freeze, I will start
> moving JIRAs out of this release.
>
> * Closed JIRAs: So far ~191 closed tickets for 0.11.0.0:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.11.0.0%20ORDER%20BY%20priority%20DESC
>
> * Release features:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 has
> a "Release Features" section that will be included with the release
> notes/email for the release. I added some items to get it going. Please add
> to
> this list anything you think is worth noting.
>
> I'll plan to give another update next week just before the KIP freeze.
>
> Ismael
>
--
Signature
<http://www.openbet.com/> Michal Borowiecki
Senior Software Engineer L4
T: +44 208 742 1600
+44 203 249 8448
E: michal.borowiecki@openbet.com
W: www.openbet.com <http://www.openbet.com/>
OpenBet Ltd
Chiswick Park Building 9
566 Chiswick High Rd
London
W4 5XT
UK
<https://www.openbet.com/email_promo>
This message is confidential and intended only for the addressee. If you
have received this message in error, please immediately notify the
postmaster@openbet.com <ma...@openbet.com> and delete it
from your system as well as any copies. The content of e-mails as well
as traffic data may be monitored by OpenBet for employment and security
purposes. To protect the environment please do not print this e-mail
unless necessary. OpenBet Ltd. Registered Office: Chiswick Park Building
9, 566 Chiswick High Road, London, W4 5XT, United Kingdom. A company
registered in England and Wales. Registered no. 3134634. VAT no.
GB927523612