You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Denes Arvay <de...@cloudera.com> on 2017/09/04 08:21:07 UTC
[DISCUSS] Flume 1.8 release proposal
Hi Flume Community,
Almost a year passed since we've released Flume 1.7.
More than 50 commits were pushed since then, including documentation fixes,
many critical bug fixes and several important features, so I'd like to
propose to publish the next minor release of Flume.
I'd be happy to be the Release Manager with the help of Ferenc Szabo and
Marcell Hegedus who have been quite active recently, and Balazs Donat
Bessenyei who took the lion's share of the work during the previous release
- if both community and they are OK with it.
Among others the following major changes will be included in the next
release:
Fixed bugs:
- FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
live updating config
- FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
count exceeded in MemoryChannel
- FLUME-3020. Improve HDFS Sink escape sequence substitution
- FLUME-3027. Change Kafka Channel to clear offsets map after commit
- FLUME-3049. Make HDFS sink rotate more reliably in secure mode
- FLUME-3080. Close failure in HDFS Sink might cause data loss
- FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead to
data loss
- FLUME-2752. Fix AvroSource startup resource leaks
- FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
New features:
- FLUME-2171. Add Interceptor to remove headers from event
- FLUME-2993. Add support for environment variables in configuration files
- New component: HTTP Sink
- FLUME-3100. Support arbitrary header substitution for topic of Kafka Sink
- FLUME-2917. Provide netcat UDP source as alternative to TCP
There are 35 open tickets targeted for 1.8 in patch available state:
https://s.apache.org/flume-1.8-target-tickets
Plus we also have quite a lot (~65) open pull requests on GitHub:
https://github.com/apache/flume/pulls
Some of the above mentioned tickets/pull requests already have some review
comments, so at least part of this list can get into this release beside
the already pushed ones.
I'd like to propose to target the week of 11th of September with the first
release candidate. That'd mean that the branch date would be the 11th, any
significant code change should get in by that date.
If nobody has any concerns then I'm going to create an umbrella ticket to
track the release process.
Kind regards,
Denes
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Attila Simon <sa...@cloudera.com>.
Hi Denes,
I think this is a great idea! I can offer help in reviewing some of the
inflight patches/pull requests.
Cheers,
Attila
*Attila Simon*
Software Engineer
Email: sati@cloudera.com
[image: Cloudera Inc.]
On Tue, Sep 5, 2017 at 11:34 PM, Mike Percy <mp...@apache.org> wrote:
> Hi Denes,
> +1 from me for releasing a Flume 1.8.0 and for you taking on the RM role
> for Flume 1.8.0. The timeline for a first RC seems fine.
>
> It sounds like you will have some help, which is good. Let me know if you
> need anything from me.
>
> Regards,
> Mike
>
> On Mon, Sep 4, 2017 at 1:21 AM, Denes Arvay <de...@cloudera.com> wrote:
>
> > Hi Flume Community,
> >
> > Almost a year passed since we've released Flume 1.7.
> > More than 50 commits were pushed since then, including documentation
> fixes,
> > many critical bug fixes and several important features, so I'd like to
> > propose to publish the next minor release of Flume.
> >
> > I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> > Marcell Hegedus who have been quite active recently, and Balazs Donat
> > Bessenyei who took the lion's share of the work during the previous
> release
> > - if both community and they are OK with it.
> >
> > Among others the following major changes will be included in the next
> > release:
> >
> > Fixed bugs:
> > - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> > live updating config
> > - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> > count exceeded in MemoryChannel
> > - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> > - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
> to
> > data loss
> > - FLUME-2752. Fix AvroSource startup resource leaks
> > - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> >
> > New features:
> > - FLUME-2171. Add Interceptor to remove headers from event
> > - FLUME-2993. Add support for environment variables in configuration
> files
> > - New component: HTTP Sink
> > - FLUME-3100. Support arbitrary header substitution for topic of Kafka
> Sink
> > - FLUME-2917. Provide netcat UDP source as alternative to TCP
> >
> > There are 35 open tickets targeted for 1.8 in patch available state:
> > https://s.apache.org/flume-1.8-target-tickets
> >
> > Plus we also have quite a lot (~65) open pull requests on GitHub:
> > https://github.com/apache/flume/pulls
> >
> > Some of the above mentioned tickets/pull requests already have some
> review
> > comments, so at least part of this list can get into this release beside
> > the already pushed ones.
> >
> > I'd like to propose to target the week of 11th of September with the
> first
> > release candidate. That'd mean that the branch date would be the 11th,
> any
> > significant code change should get in by that date.
> >
> > If nobody has any concerns then I'm going to create an umbrella ticket to
> > track the release process.
> >
> > Kind regards,
> > Denes
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Mike Percy <mp...@apache.org>.
Hi Denes,
+1 from me for releasing a Flume 1.8.0 and for you taking on the RM role
for Flume 1.8.0. The timeline for a first RC seems fine.
It sounds like you will have some help, which is good. Let me know if you
need anything from me.
Regards,
Mike
On Mon, Sep 4, 2017 at 1:21 AM, Denes Arvay <de...@cloudera.com> wrote:
> Hi Flume Community,
>
> Almost a year passed since we've released Flume 1.7.
> More than 50 commits were pushed since then, including documentation fixes,
> many critical bug fixes and several important features, so I'd like to
> propose to publish the next minor release of Flume.
>
> I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> Marcell Hegedus who have been quite active recently, and Balazs Donat
> Bessenyei who took the lion's share of the work during the previous release
> - if both community and they are OK with it.
>
> Among others the following major changes will be included in the next
> release:
>
> Fixed bugs:
> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> live updating config
> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> count exceeded in MemoryChannel
> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead to
> data loss
> - FLUME-2752. Fix AvroSource startup resource leaks
> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
>
> New features:
> - FLUME-2171. Add Interceptor to remove headers from event
> - FLUME-2993. Add support for environment variables in configuration files
> - New component: HTTP Sink
> - FLUME-3100. Support arbitrary header substitution for topic of Kafka Sink
> - FLUME-2917. Provide netcat UDP source as alternative to TCP
>
> There are 35 open tickets targeted for 1.8 in patch available state:
> https://s.apache.org/flume-1.8-target-tickets
>
> Plus we also have quite a lot (~65) open pull requests on GitHub:
> https://github.com/apache/flume/pulls
>
> Some of the above mentioned tickets/pull requests already have some review
> comments, so at least part of this list can get into this release beside
> the already pushed ones.
>
> I'd like to propose to target the week of 11th of September with the first
> release candidate. That'd mean that the branch date would be the 11th, any
> significant code change should get in by that date.
>
> If nobody has any concerns then I'm going to create an umbrella ticket to
> track the release process.
>
> Kind regards,
> Denes
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Tristan Stevens <tr...@cloudera.com>.
Hi Denes,
+1 from me.
I’m really in support of a much more regular release cadence, especially
including maintenance releases. If there’s anything I can do to help burn
down the backlog over the coming months, then please let me know.
Let’s ship this one, then get cracking with 1.8.1.
Tristan
On 12 September 2017 at 17:15:05, Denes Arvay (denes@cloudera.com) wrote:
Hi Tristan,
I understand your concerns. I do think, though, that most of the low
hanging fruits have been committed already and there are no uncommitted
tickets with explicit +1s.
I'd like to propose to continue with the release process as planned, given
44 tickets have been resolved since the 1.7 release, plus a couple of minor
changes have been committed without Jira tickets.
I think the community has just got a bit more active as it used to be some
months ago and I'd like to use this momentum to schedule releases more
often. It'd be nice to introduce maintenance release (e.g. release 1.8.1 in
about a month) and have more frequent minors - let's say one in every 3
months.
Having a faster release cadence would mean that doing a release would need
a lot less effort and we'd do the Jira grooming more often which eventually
could lead to a clean backlog and that we could set realistic expectations
for the contributors/users on when their changes/requested features will
get into a release.
But unfortunately we are not there yet, and I think this is the reason why
some patches have been in Patch available state for months, which - I do
agree - is frustrating.
I think working through this release process is a step to the above
outlined direction, so I'd like to move forward with it.
What do you think?
Thanks,
Denes
On Tue, Sep 12, 2017 at 4:46 PM Tristan Stevens <tr...@cloudera.com>
wrote:
> FWIW:
> I’m not overly in favour of rushing a release out when we have many JIRAs
> with patches submitted, especially when some of those are +1’d by multiple
> reviewers.
>
> This doesn’t speak of a mature and active community process - I’d much
> rather that we pause a little, have a big effort by the committers to get
> these patches in - especially as this will improve buy-in for those who
> have spent time developing patches. I, for one, would be much more likely
> to be a more active member of the community if I could see my patches
> getting committed, rather than spending years in ‘patch available’.
>
> Would anyone be in favour of a concerted push to get some of these types of
> JIRAs committed?
>
> Tristan
>
> On 12 September 2017 at 14:39:45, Ferenc Szabo (fszabo@cloudera.com)
> wrote:
>
> FYI:
> jira issues have been moved to the new fix versions:
> 1.8.1:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.8.1
> 1.9.0:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.9.0
>
>
> On Tue, Sep 12, 2017 at 12:17 PM, Mike Percy <mp...@apache.org> wrote:
>
> > I added the additional versions earlier today but neglected to notify the
> > list until just now. :)
> >
> > +1 on the plan. Thanks for keeping us updated and continuing to drive
> this
> > release, Denes!
> >
> > Mike
> >
> > On Tue, Sep 12, 2017 at 3:04 AM, Denes Arvay <de...@cloudera.com> wrote:
> >
> > > Hi Donat,
> > >
> > > Thanks for your help.
> > > Ferenc Szabo is already working on the retargeting, but it's definitely
> a
> > > good advice to do it in bulk to avoid spamming the lists.
> > >
> > > We have the following action items:
> > > - retarget the tickets
> > > - fix the blockers: there is only one left which I'm aware of:
> > > https://issues.apache.org/jira/browse/FLUME-3174. To fix that
> upgrading
> > > the
> > > joda-time is in progress: https://github.com/apache/flume/pull/169
> > > - the user guide is broken (netcat udp source's table is malformed),
> I'm
> > > fixing it
> > > - https://github.com/apache/flume/pull/168 needs to be committed. I've
> > > seen
> > > that you've already commented on it, thank you, will reply soon.
> > (Spoiler:
> > > a lot of effort, unfortunately)
> > > - some minor changes need to be done in the documentation (e.g. fixing
> > the
> > > copyright dates, removing/updating the version references in the user
> > > guide). If anybody in the community feels like doing it I'd be more
> than
> > > happy to review & commit the changes.
> > > - once these are done I'm going to create the 1.8 branch and create the
> > RC1
> > > release artifact. I'll announce the branching in advance to the dev@
> > list.
> > >
> > > Thank you,
> > > Denes
> > >
> > >
> > > On Tue, Sep 12, 2017 at 11:18 AM Bessenyei Balázs Donát <
> > bessbd@apache.org
> > > >
> > > wrote:
> > >
> > > > Hi Denes,
> > > >
> > > > It seems to me that 1.8.1 and 1.9.0 releases already exist in our
> JIRA.
> > > >
> > > > Regarding the retargeting: I'd be happy to batch-edit the necessary
> > > > tickets in order to avoid spamming the mailing lists.
> > > > Once you have a list of actions you'd like to do, please let us know.
> > > >
> > > >
> > > > Thank you,
> > > >
> > > > Donat
> > > >
> > > > 2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> > > > > Hi All,
> > > > >
> > > > > I'd like to let you know that we are planning to cut the 1.8 branch
> > > > > tomorrow around 2am PDT.
> > > > > If you think that there any important tickets targeted to 1.8 still
> > > open
> > > > > which needs to be reviewed and committed to get into the release,
> > > please
> > > > > let us know as soon as possible and we'll do our best to push it
> > > through.
> > > > >
> > > > > The ones which couldn't get committed by the branching will be
> > > retargeted
> > > > > to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be
> > > > retargeted
> > > > > to 1.8.1, new features will be scheduled for 1.9).
> > > > > For this I'd like to ask our PMC members to create these new
> releases
> > > in
> > > > > Jira, or if it's possible to grant the required Jira permissions to
> > me,
> > > > I'd
> > > > > be more than happy to do this.
> > > > >
> > > > > Thank you,
> > > > > Denes
> > > > >
> > > > > On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com>
> > > wrote:
> > > > >
> > > > >> Hi Flume Community,
> > > > >>
> > > > >> Almost a year passed since we've released Flume 1.7.
> > > > >> More than 50 commits were pushed since then, including
> documentation
> > > > >> fixes, many critical bug fixes and several important features, so
> > I'd
> > > > like
> > > > >> to propose to publish the next minor release of Flume.
> > > > >>
> > > > >> I'd be happy to be the Release Manager with the help of Ferenc
> Szabo
> > > and
> > > > >> Marcell Hegedus who have been quite active recently, and Balazs
> > Donat
> > > > >> Bessenyei who took the lion's share of the work during the
> previous
> > > > release
> > > > >> - if both community and they are OK with it.
> > > > >>
> > > > >> Among others the following major changes will be included in the
> > next
> > > > >> release:
> > > > >>
> > > > >> Fixed bugs:
> > > > >> - FLUME-2857. Make Kafka Source/Channel/Sink restore default
> values
> > > when
> > > > >> live updating config
> > > > >> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum
> > > permit
> > > > >> count exceeded in MemoryChannel
> > > > >> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > > > >> - FLUME-3027. Change Kafka Channel to clear offsets map after
> commit
> > > > >> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > > > >> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > > > >> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters,
> might
> > > lead
> > > > >> to data loss
> > > > >> - FLUME-2752. Fix AvroSource startup resource leaks
> > > > >> - FLUME-2905. Fix NetcatSource file descriptor leak if startup
> fails
> > > > >>
> > > > >> New features:
> > > > >> - FLUME-2171. Add Interceptor to remove headers from event
> > > > >> - FLUME-2993. Add support for environment variables in
> configuration
> > > > files
> > > > >> - New component: HTTP Sink
> > > > >> - FLUME-3100. Support arbitrary header substitution for topic of
> > Kafka
> > > > Sink
> > > > >> - FLUME-2917. Provide netcat UDP source as alternative to TCP
> > > > >>
> > > > >> There are 35 open tickets targeted for 1.8 in patch available
> state:
> > > > >> https://s.apache.org/flume-1.8-target-tickets
> > > > >>
> > > > >> Plus we also have quite a lot (~65) open pull requests on GitHub:
> > > > >> https://github.com/apache/flume/pulls
> > > > >>
> > > > >> Some of the above mentioned tickets/pull requests already have
> some
> > > > review
> > > > >> comments, so at least part of this list can get into this release
> > > beside
> > > > >> the already pushed ones.
> > > > >>
> > > > >> I'd like to propose to target the week of 11th of September with
> the
> > > > first
> > > > >> release candidate. That'd mean that the branch date would be the
> > 11th,
> > > > any
> > > > >> significant code change should get in by that date.
> > > > >>
> > > > >> If nobody has any concerns then I'm going to create an umbrella
> > ticket
> > > > to
> > > > >> track the release process.
> > > > >>
> > > > >> Kind regards,
> > > > >> Denes
> > > > >>
> > > > >>
> > > >
> > >
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Denes Arvay <de...@cloudera.com>.
Hi Tristan,
I understand your concerns. I do think, though, that most of the low
hanging fruits have been committed already and there are no uncommitted
tickets with explicit +1s.
I'd like to propose to continue with the release process as planned, given
44 tickets have been resolved since the 1.7 release, plus a couple of minor
changes have been committed without Jira tickets.
I think the community has just got a bit more active as it used to be some
months ago and I'd like to use this momentum to schedule releases more
often. It'd be nice to introduce maintenance release (e.g. release 1.8.1 in
about a month) and have more frequent minors - let's say one in every 3
months.
Having a faster release cadence would mean that doing a release would need
a lot less effort and we'd do the Jira grooming more often which eventually
could lead to a clean backlog and that we could set realistic expectations
for the contributors/users on when their changes/requested features will
get into a release.
But unfortunately we are not there yet, and I think this is the reason why
some patches have been in Patch available state for months, which - I do
agree - is frustrating.
I think working through this release process is a step to the above
outlined direction, so I'd like to move forward with it.
What do you think?
Thanks,
Denes
On Tue, Sep 12, 2017 at 4:46 PM Tristan Stevens <tr...@cloudera.com>
wrote:
> FWIW:
> I’m not overly in favour of rushing a release out when we have many JIRAs
> with patches submitted, especially when some of those are +1’d by multiple
> reviewers.
>
> This doesn’t speak of a mature and active community process - I’d much
> rather that we pause a little, have a big effort by the committers to get
> these patches in - especially as this will improve buy-in for those who
> have spent time developing patches. I, for one, would be much more likely
> to be a more active member of the community if I could see my patches
> getting committed, rather than spending years in ‘patch available’.
>
> Would anyone be in favour of a concerted push to get some of these types of
> JIRAs committed?
>
> Tristan
>
> On 12 September 2017 at 14:39:45, Ferenc Szabo (fszabo@cloudera.com)
> wrote:
>
> FYI:
> jira issues have been moved to the new fix versions:
> 1.8.1:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.8.1
> 1.9.0:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.9.0
>
>
> On Tue, Sep 12, 2017 at 12:17 PM, Mike Percy <mp...@apache.org> wrote:
>
> > I added the additional versions earlier today but neglected to notify the
> > list until just now. :)
> >
> > +1 on the plan. Thanks for keeping us updated and continuing to drive
> this
> > release, Denes!
> >
> > Mike
> >
> > On Tue, Sep 12, 2017 at 3:04 AM, Denes Arvay <de...@cloudera.com> wrote:
> >
> > > Hi Donat,
> > >
> > > Thanks for your help.
> > > Ferenc Szabo is already working on the retargeting, but it's definitely
> a
> > > good advice to do it in bulk to avoid spamming the lists.
> > >
> > > We have the following action items:
> > > - retarget the tickets
> > > - fix the blockers: there is only one left which I'm aware of:
> > > https://issues.apache.org/jira/browse/FLUME-3174. To fix that
> upgrading
> > > the
> > > joda-time is in progress: https://github.com/apache/flume/pull/169
> > > - the user guide is broken (netcat udp source's table is malformed),
> I'm
> > > fixing it
> > > - https://github.com/apache/flume/pull/168 needs to be committed. I've
> > > seen
> > > that you've already commented on it, thank you, will reply soon.
> > (Spoiler:
> > > a lot of effort, unfortunately)
> > > - some minor changes need to be done in the documentation (e.g. fixing
> > the
> > > copyright dates, removing/updating the version references in the user
> > > guide). If anybody in the community feels like doing it I'd be more
> than
> > > happy to review & commit the changes.
> > > - once these are done I'm going to create the 1.8 branch and create the
> > RC1
> > > release artifact. I'll announce the branching in advance to the dev@
> > list.
> > >
> > > Thank you,
> > > Denes
> > >
> > >
> > > On Tue, Sep 12, 2017 at 11:18 AM Bessenyei Balázs Donát <
> > bessbd@apache.org
> > > >
> > > wrote:
> > >
> > > > Hi Denes,
> > > >
> > > > It seems to me that 1.8.1 and 1.9.0 releases already exist in our
> JIRA.
> > > >
> > > > Regarding the retargeting: I'd be happy to batch-edit the necessary
> > > > tickets in order to avoid spamming the mailing lists.
> > > > Once you have a list of actions you'd like to do, please let us know.
> > > >
> > > >
> > > > Thank you,
> > > >
> > > > Donat
> > > >
> > > > 2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> > > > > Hi All,
> > > > >
> > > > > I'd like to let you know that we are planning to cut the 1.8 branch
> > > > > tomorrow around 2am PDT.
> > > > > If you think that there any important tickets targeted to 1.8 still
> > > open
> > > > > which needs to be reviewed and committed to get into the release,
> > > please
> > > > > let us know as soon as possible and we'll do our best to push it
> > > through.
> > > > >
> > > > > The ones which couldn't get committed by the branching will be
> > > retargeted
> > > > > to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be
> > > > retargeted
> > > > > to 1.8.1, new features will be scheduled for 1.9).
> > > > > For this I'd like to ask our PMC members to create these new
> releases
> > > in
> > > > > Jira, or if it's possible to grant the required Jira permissions to
> > me,
> > > > I'd
> > > > > be more than happy to do this.
> > > > >
> > > > > Thank you,
> > > > > Denes
> > > > >
> > > > > On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com>
> > > wrote:
> > > > >
> > > > >> Hi Flume Community,
> > > > >>
> > > > >> Almost a year passed since we've released Flume 1.7.
> > > > >> More than 50 commits were pushed since then, including
> documentation
> > > > >> fixes, many critical bug fixes and several important features, so
> > I'd
> > > > like
> > > > >> to propose to publish the next minor release of Flume.
> > > > >>
> > > > >> I'd be happy to be the Release Manager with the help of Ferenc
> Szabo
> > > and
> > > > >> Marcell Hegedus who have been quite active recently, and Balazs
> > Donat
> > > > >> Bessenyei who took the lion's share of the work during the
> previous
> > > > release
> > > > >> - if both community and they are OK with it.
> > > > >>
> > > > >> Among others the following major changes will be included in the
> > next
> > > > >> release:
> > > > >>
> > > > >> Fixed bugs:
> > > > >> - FLUME-2857. Make Kafka Source/Channel/Sink restore default
> values
> > > when
> > > > >> live updating config
> > > > >> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum
> > > permit
> > > > >> count exceeded in MemoryChannel
> > > > >> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > > > >> - FLUME-3027. Change Kafka Channel to clear offsets map after
> commit
> > > > >> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > > > >> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > > > >> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters,
> might
> > > lead
> > > > >> to data loss
> > > > >> - FLUME-2752. Fix AvroSource startup resource leaks
> > > > >> - FLUME-2905. Fix NetcatSource file descriptor leak if startup
> fails
> > > > >>
> > > > >> New features:
> > > > >> - FLUME-2171. Add Interceptor to remove headers from event
> > > > >> - FLUME-2993. Add support for environment variables in
> configuration
> > > > files
> > > > >> - New component: HTTP Sink
> > > > >> - FLUME-3100. Support arbitrary header substitution for topic of
> > Kafka
> > > > Sink
> > > > >> - FLUME-2917. Provide netcat UDP source as alternative to TCP
> > > > >>
> > > > >> There are 35 open tickets targeted for 1.8 in patch available
> state:
> > > > >> https://s.apache.org/flume-1.8-target-tickets
> > > > >>
> > > > >> Plus we also have quite a lot (~65) open pull requests on GitHub:
> > > > >> https://github.com/apache/flume/pulls
> > > > >>
> > > > >> Some of the above mentioned tickets/pull requests already have
> some
> > > > review
> > > > >> comments, so at least part of this list can get into this release
> > > beside
> > > > >> the already pushed ones.
> > > > >>
> > > > >> I'd like to propose to target the week of 11th of September with
> the
> > > > first
> > > > >> release candidate. That'd mean that the branch date would be the
> > 11th,
> > > > any
> > > > >> significant code change should get in by that date.
> > > > >>
> > > > >> If nobody has any concerns then I'm going to create an umbrella
> > ticket
> > > > to
> > > > >> track the release process.
> > > > >>
> > > > >> Kind regards,
> > > > >> Denes
> > > > >>
> > > > >>
> > > >
> > >
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Denes Arvay <de...@cloudera.com>.
Thank you all for sharing your thoughts, and thanks Tristan for supporting
the release.
I'm about to branch, I'll let you know when it's done.
Regards,
Denes
On Wed, Sep 13, 2017 at 6:10 AM Ralph Goers <ra...@dslextreme.com>
wrote:
>
> > On Sep 12, 2017, at 7:46 AM, Tristan Stevens <tr...@cloudera.com>
> wrote:
> >
> > FWIW:
> > I’m not overly in favour of rushing a release out when we have many JIRAs
> > with patches submitted, especially when some of those are +1’d by
> multiple
> > reviewers.
>
> Rushing a release? It has been a year since the last release. For most
> open source projects that is an eternity.
>
> >
> > This doesn’t speak of a mature and active community process - I’d much
> > rather that we pause a little, have a big effort by the committers to get
> > these patches in - especially as this will improve buy-in for those who
> > have spent time developing patches. I, for one, would be much more likely
> > to be a more active member of the community if I could see my patches
> > getting committed, rather than spending years in ‘patch available’.
> >
> > Would anyone be in favour of a concerted push to get some of these types
> of
> > JIRAs committed?
>
> From my experience you will not gain anything. People have had a year to
> fix the things that interest them. Waiting a bit longer just means more
> things will come in that people think are important.
>
> The solution is the same as it always has been. Release early and release
> often. You wouldn’t even be suggesting this if you knew another release
> would be coming next month.
>
> Ralph
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Ralph Goers <ra...@dslextreme.com>.
> On Sep 12, 2017, at 7:46 AM, Tristan Stevens <tr...@cloudera.com> wrote:
>
> FWIW:
> I’m not overly in favour of rushing a release out when we have many JIRAs
> with patches submitted, especially when some of those are +1’d by multiple
> reviewers.
Rushing a release? It has been a year since the last release. For most open source projects that is an eternity.
>
> This doesn’t speak of a mature and active community process - I’d much
> rather that we pause a little, have a big effort by the committers to get
> these patches in - especially as this will improve buy-in for those who
> have spent time developing patches. I, for one, would be much more likely
> to be a more active member of the community if I could see my patches
> getting committed, rather than spending years in ‘patch available’.
>
> Would anyone be in favour of a concerted push to get some of these types of
> JIRAs committed?
From my experience you will not gain anything. People have had a year to fix the things that interest them. Waiting a bit longer just means more things will come in that people think are important.
The solution is the same as it always has been. Release early and release often. You wouldn’t even be suggesting this if you knew another release would be coming next month.
Ralph
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Tristan Stevens <tr...@cloudera.com>.
FWIW:
I’m not overly in favour of rushing a release out when we have many JIRAs
with patches submitted, especially when some of those are +1’d by multiple
reviewers.
This doesn’t speak of a mature and active community process - I’d much
rather that we pause a little, have a big effort by the committers to get
these patches in - especially as this will improve buy-in for those who
have spent time developing patches. I, for one, would be much more likely
to be a more active member of the community if I could see my patches
getting committed, rather than spending years in ‘patch available’.
Would anyone be in favour of a concerted push to get some of these types of
JIRAs committed?
Tristan
On 12 September 2017 at 14:39:45, Ferenc Szabo (fszabo@cloudera.com) wrote:
FYI:
jira issues have been moved to the new fix versions:
1.8.1:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.8.1
1.9.0:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.9.0
On Tue, Sep 12, 2017 at 12:17 PM, Mike Percy <mp...@apache.org> wrote:
> I added the additional versions earlier today but neglected to notify the
> list until just now. :)
>
> +1 on the plan. Thanks for keeping us updated and continuing to drive
this
> release, Denes!
>
> Mike
>
> On Tue, Sep 12, 2017 at 3:04 AM, Denes Arvay <de...@cloudera.com> wrote:
>
> > Hi Donat,
> >
> > Thanks for your help.
> > Ferenc Szabo is already working on the retargeting, but it's definitely
a
> > good advice to do it in bulk to avoid spamming the lists.
> >
> > We have the following action items:
> > - retarget the tickets
> > - fix the blockers: there is only one left which I'm aware of:
> > https://issues.apache.org/jira/browse/FLUME-3174. To fix that upgrading
> > the
> > joda-time is in progress: https://github.com/apache/flume/pull/169
> > - the user guide is broken (netcat udp source's table is malformed),
I'm
> > fixing it
> > - https://github.com/apache/flume/pull/168 needs to be committed. I've
> > seen
> > that you've already commented on it, thank you, will reply soon.
> (Spoiler:
> > a lot of effort, unfortunately)
> > - some minor changes need to be done in the documentation (e.g. fixing
> the
> > copyright dates, removing/updating the version references in the user
> > guide). If anybody in the community feels like doing it I'd be more
than
> > happy to review & commit the changes.
> > - once these are done I'm going to create the 1.8 branch and create the
> RC1
> > release artifact. I'll announce the branching in advance to the dev@
> list.
> >
> > Thank you,
> > Denes
> >
> >
> > On Tue, Sep 12, 2017 at 11:18 AM Bessenyei Balázs Donát <
> bessbd@apache.org
> > >
> > wrote:
> >
> > > Hi Denes,
> > >
> > > It seems to me that 1.8.1 and 1.9.0 releases already exist in our
JIRA.
> > >
> > > Regarding the retargeting: I'd be happy to batch-edit the necessary
> > > tickets in order to avoid spamming the mailing lists.
> > > Once you have a list of actions you'd like to do, please let us know.
> > >
> > >
> > > Thank you,
> > >
> > > Donat
> > >
> > > 2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> > > > Hi All,
> > > >
> > > > I'd like to let you know that we are planning to cut the 1.8 branch
> > > > tomorrow around 2am PDT.
> > > > If you think that there any important tickets targeted to 1.8 still
> > open
> > > > which needs to be reviewed and committed to get into the release,
> > please
> > > > let us know as soon as possible and we'll do our best to push it
> > through.
> > > >
> > > > The ones which couldn't get committed by the branching will be
> > retargeted
> > > > to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be
> > > retargeted
> > > > to 1.8.1, new features will be scheduled for 1.9).
> > > > For this I'd like to ask our PMC members to create these new
releases
> > in
> > > > Jira, or if it's possible to grant the required Jira permissions to
> me,
> > > I'd
> > > > be more than happy to do this.
> > > >
> > > > Thank you,
> > > > Denes
> > > >
> > > > On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com>
> > wrote:
> > > >
> > > >> Hi Flume Community,
> > > >>
> > > >> Almost a year passed since we've released Flume 1.7.
> > > >> More than 50 commits were pushed since then, including
documentation
> > > >> fixes, many critical bug fixes and several important features, so
> I'd
> > > like
> > > >> to propose to publish the next minor release of Flume.
> > > >>
> > > >> I'd be happy to be the Release Manager with the help of Ferenc
Szabo
> > and
> > > >> Marcell Hegedus who have been quite active recently, and Balazs
> Donat
> > > >> Bessenyei who took the lion's share of the work during the
previous
> > > release
> > > >> - if both community and they are OK with it.
> > > >>
> > > >> Among others the following major changes will be included in the
> next
> > > >> release:
> > > >>
> > > >> Fixed bugs:
> > > >> - FLUME-2857. Make Kafka Source/Channel/Sink restore default
values
> > when
> > > >> live updating config
> > > >> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum
> > permit
> > > >> count exceeded in MemoryChannel
> > > >> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > > >> - FLUME-3027. Change Kafka Channel to clear offsets map after
commit
> > > >> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > > >> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > > >> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters,
might
> > lead
> > > >> to data loss
> > > >> - FLUME-2752. Fix AvroSource startup resource leaks
> > > >> - FLUME-2905. Fix NetcatSource file descriptor leak if startup
fails
> > > >>
> > > >> New features:
> > > >> - FLUME-2171. Add Interceptor to remove headers from event
> > > >> - FLUME-2993. Add support for environment variables in
configuration
> > > files
> > > >> - New component: HTTP Sink
> > > >> - FLUME-3100. Support arbitrary header substitution for topic of
> Kafka
> > > Sink
> > > >> - FLUME-2917. Provide netcat UDP source as alternative to TCP
> > > >>
> > > >> There are 35 open tickets targeted for 1.8 in patch available
state:
> > > >> https://s.apache.org/flume-1.8-target-tickets
> > > >>
> > > >> Plus we also have quite a lot (~65) open pull requests on GitHub:
> > > >> https://github.com/apache/flume/pulls
> > > >>
> > > >> Some of the above mentioned tickets/pull requests already have
some
> > > review
> > > >> comments, so at least part of this list can get into this release
> > beside
> > > >> the already pushed ones.
> > > >>
> > > >> I'd like to propose to target the week of 11th of September with
the
> > > first
> > > >> release candidate. That'd mean that the branch date would be the
> 11th,
> > > any
> > > >> significant code change should get in by that date.
> > > >>
> > > >> If nobody has any concerns then I'm going to create an umbrella
> ticket
> > > to
> > > >> track the release process.
> > > >>
> > > >> Kind regards,
> > > >> Denes
> > > >>
> > > >>
> > >
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Ferenc Szabo <fs...@cloudera.com>.
FYI:
jira issues have been moved to the new fix versions:
1.8.1:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.8.1
1.9.0:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%201.9.0
On Tue, Sep 12, 2017 at 12:17 PM, Mike Percy <mp...@apache.org> wrote:
> I added the additional versions earlier today but neglected to notify the
> list until just now. :)
>
> +1 on the plan. Thanks for keeping us updated and continuing to drive this
> release, Denes!
>
> Mike
>
> On Tue, Sep 12, 2017 at 3:04 AM, Denes Arvay <de...@cloudera.com> wrote:
>
> > Hi Donat,
> >
> > Thanks for your help.
> > Ferenc Szabo is already working on the retargeting, but it's definitely a
> > good advice to do it in bulk to avoid spamming the lists.
> >
> > We have the following action items:
> > - retarget the tickets
> > - fix the blockers: there is only one left which I'm aware of:
> > https://issues.apache.org/jira/browse/FLUME-3174. To fix that upgrading
> > the
> > joda-time is in progress: https://github.com/apache/flume/pull/169
> > - the user guide is broken (netcat udp source's table is malformed), I'm
> > fixing it
> > - https://github.com/apache/flume/pull/168 needs to be committed. I've
> > seen
> > that you've already commented on it, thank you, will reply soon.
> (Spoiler:
> > a lot of effort, unfortunately)
> > - some minor changes need to be done in the documentation (e.g. fixing
> the
> > copyright dates, removing/updating the version references in the user
> > guide). If anybody in the community feels like doing it I'd be more than
> > happy to review & commit the changes.
> > - once these are done I'm going to create the 1.8 branch and create the
> RC1
> > release artifact. I'll announce the branching in advance to the dev@
> list.
> >
> > Thank you,
> > Denes
> >
> >
> > On Tue, Sep 12, 2017 at 11:18 AM Bessenyei Balázs Donát <
> bessbd@apache.org
> > >
> > wrote:
> >
> > > Hi Denes,
> > >
> > > It seems to me that 1.8.1 and 1.9.0 releases already exist in our JIRA.
> > >
> > > Regarding the retargeting: I'd be happy to batch-edit the necessary
> > > tickets in order to avoid spamming the mailing lists.
> > > Once you have a list of actions you'd like to do, please let us know.
> > >
> > >
> > > Thank you,
> > >
> > > Donat
> > >
> > > 2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> > > > Hi All,
> > > >
> > > > I'd like to let you know that we are planning to cut the 1.8 branch
> > > > tomorrow around 2am PDT.
> > > > If you think that there any important tickets targeted to 1.8 still
> > open
> > > > which needs to be reviewed and committed to get into the release,
> > please
> > > > let us know as soon as possible and we'll do our best to push it
> > through.
> > > >
> > > > The ones which couldn't get committed by the branching will be
> > retargeted
> > > > to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be
> > > retargeted
> > > > to 1.8.1, new features will be scheduled for 1.9).
> > > > For this I'd like to ask our PMC members to create these new releases
> > in
> > > > Jira, or if it's possible to grant the required Jira permissions to
> me,
> > > I'd
> > > > be more than happy to do this.
> > > >
> > > > Thank you,
> > > > Denes
> > > >
> > > > On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com>
> > wrote:
> > > >
> > > >> Hi Flume Community,
> > > >>
> > > >> Almost a year passed since we've released Flume 1.7.
> > > >> More than 50 commits were pushed since then, including documentation
> > > >> fixes, many critical bug fixes and several important features, so
> I'd
> > > like
> > > >> to propose to publish the next minor release of Flume.
> > > >>
> > > >> I'd be happy to be the Release Manager with the help of Ferenc Szabo
> > and
> > > >> Marcell Hegedus who have been quite active recently, and Balazs
> Donat
> > > >> Bessenyei who took the lion's share of the work during the previous
> > > release
> > > >> - if both community and they are OK with it.
> > > >>
> > > >> Among others the following major changes will be included in the
> next
> > > >> release:
> > > >>
> > > >> Fixed bugs:
> > > >> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values
> > when
> > > >> live updating config
> > > >> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum
> > permit
> > > >> count exceeded in MemoryChannel
> > > >> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > > >> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> > > >> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > > >> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > > >> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might
> > lead
> > > >> to data loss
> > > >> - FLUME-2752. Fix AvroSource startup resource leaks
> > > >> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> > > >>
> > > >> New features:
> > > >> - FLUME-2171. Add Interceptor to remove headers from event
> > > >> - FLUME-2993. Add support for environment variables in configuration
> > > files
> > > >> - New component: HTTP Sink
> > > >> - FLUME-3100. Support arbitrary header substitution for topic of
> Kafka
> > > Sink
> > > >> - FLUME-2917. Provide netcat UDP source as alternative to TCP
> > > >>
> > > >> There are 35 open tickets targeted for 1.8 in patch available state:
> > > >> https://s.apache.org/flume-1.8-target-tickets
> > > >>
> > > >> Plus we also have quite a lot (~65) open pull requests on GitHub:
> > > >> https://github.com/apache/flume/pulls
> > > >>
> > > >> Some of the above mentioned tickets/pull requests already have some
> > > review
> > > >> comments, so at least part of this list can get into this release
> > beside
> > > >> the already pushed ones.
> > > >>
> > > >> I'd like to propose to target the week of 11th of September with the
> > > first
> > > >> release candidate. That'd mean that the branch date would be the
> 11th,
> > > any
> > > >> significant code change should get in by that date.
> > > >>
> > > >> If nobody has any concerns then I'm going to create an umbrella
> ticket
> > > to
> > > >> track the release process.
> > > >>
> > > >> Kind regards,
> > > >> Denes
> > > >>
> > > >>
> > >
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Mike Percy <mp...@apache.org>.
I added the additional versions earlier today but neglected to notify the
list until just now. :)
+1 on the plan. Thanks for keeping us updated and continuing to drive this
release, Denes!
Mike
On Tue, Sep 12, 2017 at 3:04 AM, Denes Arvay <de...@cloudera.com> wrote:
> Hi Donat,
>
> Thanks for your help.
> Ferenc Szabo is already working on the retargeting, but it's definitely a
> good advice to do it in bulk to avoid spamming the lists.
>
> We have the following action items:
> - retarget the tickets
> - fix the blockers: there is only one left which I'm aware of:
> https://issues.apache.org/jira/browse/FLUME-3174. To fix that upgrading
> the
> joda-time is in progress: https://github.com/apache/flume/pull/169
> - the user guide is broken (netcat udp source's table is malformed), I'm
> fixing it
> - https://github.com/apache/flume/pull/168 needs to be committed. I've
> seen
> that you've already commented on it, thank you, will reply soon. (Spoiler:
> a lot of effort, unfortunately)
> - some minor changes need to be done in the documentation (e.g. fixing the
> copyright dates, removing/updating the version references in the user
> guide). If anybody in the community feels like doing it I'd be more than
> happy to review & commit the changes.
> - once these are done I'm going to create the 1.8 branch and create the RC1
> release artifact. I'll announce the branching in advance to the dev@ list.
>
> Thank you,
> Denes
>
>
> On Tue, Sep 12, 2017 at 11:18 AM Bessenyei Balázs Donát <bessbd@apache.org
> >
> wrote:
>
> > Hi Denes,
> >
> > It seems to me that 1.8.1 and 1.9.0 releases already exist in our JIRA.
> >
> > Regarding the retargeting: I'd be happy to batch-edit the necessary
> > tickets in order to avoid spamming the mailing lists.
> > Once you have a list of actions you'd like to do, please let us know.
> >
> >
> > Thank you,
> >
> > Donat
> >
> > 2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> > > Hi All,
> > >
> > > I'd like to let you know that we are planning to cut the 1.8 branch
> > > tomorrow around 2am PDT.
> > > If you think that there any important tickets targeted to 1.8 still
> open
> > > which needs to be reviewed and committed to get into the release,
> please
> > > let us know as soon as possible and we'll do our best to push it
> through.
> > >
> > > The ones which couldn't get committed by the branching will be
> retargeted
> > > to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be
> > retargeted
> > > to 1.8.1, new features will be scheduled for 1.9).
> > > For this I'd like to ask our PMC members to create these new releases
> in
> > > Jira, or if it's possible to grant the required Jira permissions to me,
> > I'd
> > > be more than happy to do this.
> > >
> > > Thank you,
> > > Denes
> > >
> > > On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com>
> wrote:
> > >
> > >> Hi Flume Community,
> > >>
> > >> Almost a year passed since we've released Flume 1.7.
> > >> More than 50 commits were pushed since then, including documentation
> > >> fixes, many critical bug fixes and several important features, so I'd
> > like
> > >> to propose to publish the next minor release of Flume.
> > >>
> > >> I'd be happy to be the Release Manager with the help of Ferenc Szabo
> and
> > >> Marcell Hegedus who have been quite active recently, and Balazs Donat
> > >> Bessenyei who took the lion's share of the work during the previous
> > release
> > >> - if both community and they are OK with it.
> > >>
> > >> Among others the following major changes will be included in the next
> > >> release:
> > >>
> > >> Fixed bugs:
> > >> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values
> when
> > >> live updating config
> > >> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum
> permit
> > >> count exceeded in MemoryChannel
> > >> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > >> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> > >> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > >> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > >> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might
> lead
> > >> to data loss
> > >> - FLUME-2752. Fix AvroSource startup resource leaks
> > >> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> > >>
> > >> New features:
> > >> - FLUME-2171. Add Interceptor to remove headers from event
> > >> - FLUME-2993. Add support for environment variables in configuration
> > files
> > >> - New component: HTTP Sink
> > >> - FLUME-3100. Support arbitrary header substitution for topic of Kafka
> > Sink
> > >> - FLUME-2917. Provide netcat UDP source as alternative to TCP
> > >>
> > >> There are 35 open tickets targeted for 1.8 in patch available state:
> > >> https://s.apache.org/flume-1.8-target-tickets
> > >>
> > >> Plus we also have quite a lot (~65) open pull requests on GitHub:
> > >> https://github.com/apache/flume/pulls
> > >>
> > >> Some of the above mentioned tickets/pull requests already have some
> > review
> > >> comments, so at least part of this list can get into this release
> beside
> > >> the already pushed ones.
> > >>
> > >> I'd like to propose to target the week of 11th of September with the
> > first
> > >> release candidate. That'd mean that the branch date would be the 11th,
> > any
> > >> significant code change should get in by that date.
> > >>
> > >> If nobody has any concerns then I'm going to create an umbrella ticket
> > to
> > >> track the release process.
> > >>
> > >> Kind regards,
> > >> Denes
> > >>
> > >>
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Denes Arvay <de...@cloudera.com>.
Hi Donat,
Thanks for your help.
Ferenc Szabo is already working on the retargeting, but it's definitely a
good advice to do it in bulk to avoid spamming the lists.
We have the following action items:
- retarget the tickets
- fix the blockers: there is only one left which I'm aware of:
https://issues.apache.org/jira/browse/FLUME-3174. To fix that upgrading the
joda-time is in progress: https://github.com/apache/flume/pull/169
- the user guide is broken (netcat udp source's table is malformed), I'm
fixing it
- https://github.com/apache/flume/pull/168 needs to be committed. I've seen
that you've already commented on it, thank you, will reply soon. (Spoiler:
a lot of effort, unfortunately)
- some minor changes need to be done in the documentation (e.g. fixing the
copyright dates, removing/updating the version references in the user
guide). If anybody in the community feels like doing it I'd be more than
happy to review & commit the changes.
- once these are done I'm going to create the 1.8 branch and create the RC1
release artifact. I'll announce the branching in advance to the dev@ list.
Thank you,
Denes
On Tue, Sep 12, 2017 at 11:18 AM Bessenyei Balázs Donát <be...@apache.org>
wrote:
> Hi Denes,
>
> It seems to me that 1.8.1 and 1.9.0 releases already exist in our JIRA.
>
> Regarding the retargeting: I'd be happy to batch-edit the necessary
> tickets in order to avoid spamming the mailing lists.
> Once you have a list of actions you'd like to do, please let us know.
>
>
> Thank you,
>
> Donat
>
> 2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> > Hi All,
> >
> > I'd like to let you know that we are planning to cut the 1.8 branch
> > tomorrow around 2am PDT.
> > If you think that there any important tickets targeted to 1.8 still open
> > which needs to be reviewed and committed to get into the release, please
> > let us know as soon as possible and we'll do our best to push it through.
> >
> > The ones which couldn't get committed by the branching will be retargeted
> > to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be
> retargeted
> > to 1.8.1, new features will be scheduled for 1.9).
> > For this I'd like to ask our PMC members to create these new releases in
> > Jira, or if it's possible to grant the required Jira permissions to me,
> I'd
> > be more than happy to do this.
> >
> > Thank you,
> > Denes
> >
> > On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com> wrote:
> >
> >> Hi Flume Community,
> >>
> >> Almost a year passed since we've released Flume 1.7.
> >> More than 50 commits were pushed since then, including documentation
> >> fixes, many critical bug fixes and several important features, so I'd
> like
> >> to propose to publish the next minor release of Flume.
> >>
> >> I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> >> Marcell Hegedus who have been quite active recently, and Balazs Donat
> >> Bessenyei who took the lion's share of the work during the previous
> release
> >> - if both community and they are OK with it.
> >>
> >> Among others the following major changes will be included in the next
> >> release:
> >>
> >> Fixed bugs:
> >> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> >> live updating config
> >> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> >> count exceeded in MemoryChannel
> >> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> >> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> >> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> >> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> >> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
> >> to data loss
> >> - FLUME-2752. Fix AvroSource startup resource leaks
> >> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> >>
> >> New features:
> >> - FLUME-2171. Add Interceptor to remove headers from event
> >> - FLUME-2993. Add support for environment variables in configuration
> files
> >> - New component: HTTP Sink
> >> - FLUME-3100. Support arbitrary header substitution for topic of Kafka
> Sink
> >> - FLUME-2917. Provide netcat UDP source as alternative to TCP
> >>
> >> There are 35 open tickets targeted for 1.8 in patch available state:
> >> https://s.apache.org/flume-1.8-target-tickets
> >>
> >> Plus we also have quite a lot (~65) open pull requests on GitHub:
> >> https://github.com/apache/flume/pulls
> >>
> >> Some of the above mentioned tickets/pull requests already have some
> review
> >> comments, so at least part of this list can get into this release beside
> >> the already pushed ones.
> >>
> >> I'd like to propose to target the week of 11th of September with the
> first
> >> release candidate. That'd mean that the branch date would be the 11th,
> any
> >> significant code change should get in by that date.
> >>
> >> If nobody has any concerns then I'm going to create an umbrella ticket
> to
> >> track the release process.
> >>
> >> Kind regards,
> >> Denes
> >>
> >>
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Bessenyei Balázs Donát <be...@apache.org>.
Hi Denes,
It seems to me that 1.8.1 and 1.9.0 releases already exist in our JIRA.
Regarding the retargeting: I'd be happy to batch-edit the necessary
tickets in order to avoid spamming the mailing lists.
Once you have a list of actions you'd like to do, please let us know.
Thank you,
Donat
2017-09-11 19:39 GMT+02:00 Denes Arvay <de...@cloudera.com>:
> Hi All,
>
> I'd like to let you know that we are planning to cut the 1.8 branch
> tomorrow around 2am PDT.
> If you think that there any important tickets targeted to 1.8 still open
> which needs to be reviewed and committed to get into the release, please
> let us know as soon as possible and we'll do our best to push it through.
>
> The ones which couldn't get committed by the branching will be retargeted
> to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be retargeted
> to 1.8.1, new features will be scheduled for 1.9).
> For this I'd like to ask our PMC members to create these new releases in
> Jira, or if it's possible to grant the required Jira permissions to me, I'd
> be more than happy to do this.
>
> Thank you,
> Denes
>
> On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com> wrote:
>
>> Hi Flume Community,
>>
>> Almost a year passed since we've released Flume 1.7.
>> More than 50 commits were pushed since then, including documentation
>> fixes, many critical bug fixes and several important features, so I'd like
>> to propose to publish the next minor release of Flume.
>>
>> I'd be happy to be the Release Manager with the help of Ferenc Szabo and
>> Marcell Hegedus who have been quite active recently, and Balazs Donat
>> Bessenyei who took the lion's share of the work during the previous release
>> - if both community and they are OK with it.
>>
>> Among others the following major changes will be included in the next
>> release:
>>
>> Fixed bugs:
>> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
>> live updating config
>> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
>> count exceeded in MemoryChannel
>> - FLUME-3020. Improve HDFS Sink escape sequence substitution
>> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
>> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
>> - FLUME-3080. Close failure in HDFS Sink might cause data loss
>> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
>> to data loss
>> - FLUME-2752. Fix AvroSource startup resource leaks
>> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
>>
>> New features:
>> - FLUME-2171. Add Interceptor to remove headers from event
>> - FLUME-2993. Add support for environment variables in configuration files
>> - New component: HTTP Sink
>> - FLUME-3100. Support arbitrary header substitution for topic of Kafka Sink
>> - FLUME-2917. Provide netcat UDP source as alternative to TCP
>>
>> There are 35 open tickets targeted for 1.8 in patch available state:
>> https://s.apache.org/flume-1.8-target-tickets
>>
>> Plus we also have quite a lot (~65) open pull requests on GitHub:
>> https://github.com/apache/flume/pulls
>>
>> Some of the above mentioned tickets/pull requests already have some review
>> comments, so at least part of this list can get into this release beside
>> the already pushed ones.
>>
>> I'd like to propose to target the week of 11th of September with the first
>> release candidate. That'd mean that the branch date would be the 11th, any
>> significant code change should get in by that date.
>>
>> If nobody has any concerns then I'm going to create an umbrella ticket to
>> track the release process.
>>
>> Kind regards,
>> Denes
>>
>>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Denes Arvay <de...@cloudera.com>.
Hi All,
I'd like to let you know that we are planning to cut the 1.8 branch
tomorrow around 2am PDT.
If you think that there any important tickets targeted to 1.8 still open
which needs to be reviewed and committed to get into the release, please
let us know as soon as possible and we'll do our best to push it through.
The ones which couldn't get committed by the branching will be retargeted
to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be retargeted
to 1.8.1, new features will be scheduled for 1.9).
For this I'd like to ask our PMC members to create these new releases in
Jira, or if it's possible to grant the required Jira permissions to me, I'd
be more than happy to do this.
Thank you,
Denes
On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <de...@cloudera.com> wrote:
> Hi Flume Community,
>
> Almost a year passed since we've released Flume 1.7.
> More than 50 commits were pushed since then, including documentation
> fixes, many critical bug fixes and several important features, so I'd like
> to propose to publish the next minor release of Flume.
>
> I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> Marcell Hegedus who have been quite active recently, and Balazs Donat
> Bessenyei who took the lion's share of the work during the previous release
> - if both community and they are OK with it.
>
> Among others the following major changes will be included in the next
> release:
>
> Fixed bugs:
> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> live updating config
> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> count exceeded in MemoryChannel
> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
> to data loss
> - FLUME-2752. Fix AvroSource startup resource leaks
> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
>
> New features:
> - FLUME-2171. Add Interceptor to remove headers from event
> - FLUME-2993. Add support for environment variables in configuration files
> - New component: HTTP Sink
> - FLUME-3100. Support arbitrary header substitution for topic of Kafka Sink
> - FLUME-2917. Provide netcat UDP source as alternative to TCP
>
> There are 35 open tickets targeted for 1.8 in patch available state:
> https://s.apache.org/flume-1.8-target-tickets
>
> Plus we also have quite a lot (~65) open pull requests on GitHub:
> https://github.com/apache/flume/pulls
>
> Some of the above mentioned tickets/pull requests already have some review
> comments, so at least part of this list can get into this release beside
> the already pushed ones.
>
> I'd like to propose to target the week of 11th of September with the first
> release candidate. That'd mean that the branch date would be the 11th, any
> significant code change should get in by that date.
>
> If nobody has any concerns then I'm going to create an umbrella ticket to
> track the release process.
>
> Kind regards,
> Denes
>
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Ferenc Szabo <fs...@cloudera.com>.
Dear contributors,
as part of the release we need to set the proper fix versions for the jira
issues, so with this issue: https://issues.apache.org/jira/browse/FLUME-3163
I will remove the fix version form the unresolved tickets where the time
until the release is too short to test and commit the patch.
Those will be moved to the next release which will come soon.
If there is a fix that you feel like it must be in this release, please
tell us as soon as possible, so we could discuss, review and commit it.
Thanks,
Ferenc
On Fri, Sep 8, 2017 at 11:55 AM, Denes Arvay <de...@cloudera.com> wrote:
> Hi Ferenc,
>
> Thank you.
> Could you please also create the other sub tasks required for the release?
> You can have a look on the 1.7 release umbrella ticket:
> https://issues.apache.org/jira/browse/FLUME-2924
>
> Thanks in advance,
> Denes
>
> On Fri, Sep 8, 2017 at 9:58 AM Ferenc Szabo <fs...@cloudera.com> wrote:
>
> > Hi Denes,
> >
> > sounds like a plan, I am more than happy to help, thank you for the
> > opportunity.
> > I created the umbrella ticket for the release:
> > https://issues.apache.org/jira/browse/FLUME-3162
> >
> > Let me know if any help need.
> > Best regards,
> > Ferenc Szabo
> >
> > On Mon, Sep 4, 2017 at 10:21 AM, Denes Arvay <de...@cloudera.com> wrote:
> >
> > > Hi Flume Community,
> > >
> > > Almost a year passed since we've released Flume 1.7.
> > > More than 50 commits were pushed since then, including documentation
> > fixes,
> > > many critical bug fixes and several important features, so I'd like to
> > > propose to publish the next minor release of Flume.
> > >
> > > I'd be happy to be the Release Manager with the help of Ferenc Szabo
> and
> > > Marcell Hegedus who have been quite active recently, and Balazs Donat
> > > Bessenyei who took the lion's share of the work during the previous
> > release
> > > - if both community and they are OK with it.
> > >
> > > Among others the following major changes will be included in the next
> > > release:
> > >
> > > Fixed bugs:
> > > - FLUME-2857. Make Kafka Source/Channel/Sink restore default values
> when
> > > live updating config
> > > - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum
> permit
> > > count exceeded in MemoryChannel
> > > - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > > - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> > > - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > > - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > > - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might
> lead
> > to
> > > data loss
> > > - FLUME-2752. Fix AvroSource startup resource leaks
> > > - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> > >
> > > New features:
> > > - FLUME-2171. Add Interceptor to remove headers from event
> > > - FLUME-2993. Add support for environment variables in configuration
> > files
> > > - New component: HTTP Sink
> > > - FLUME-3100. Support arbitrary header substitution for topic of Kafka
> > Sink
> > > - FLUME-2917. Provide netcat UDP source as alternative to TCP
> > >
> > > There are 35 open tickets targeted for 1.8 in patch available state:
> > > https://s.apache.org/flume-1.8-target-tickets
> > >
> > > Plus we also have quite a lot (~65) open pull requests on GitHub:
> > > https://github.com/apache/flume/pulls
> > >
> > > Some of the above mentioned tickets/pull requests already have some
> > review
> > > comments, so at least part of this list can get into this release
> beside
> > > the already pushed ones.
> > >
> > > I'd like to propose to target the week of 11th of September with the
> > first
> > > release candidate. That'd mean that the branch date would be the 11th,
> > any
> > > significant code change should get in by that date.
> > >
> > > If nobody has any concerns then I'm going to create an umbrella ticket
> to
> > > track the release process.
> > >
> > > Kind regards,
> > > Denes
> > >
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Denes Arvay <de...@cloudera.com>.
Hi Ferenc,
Thank you.
Could you please also create the other sub tasks required for the release?
You can have a look on the 1.7 release umbrella ticket:
https://issues.apache.org/jira/browse/FLUME-2924
Thanks in advance,
Denes
On Fri, Sep 8, 2017 at 9:58 AM Ferenc Szabo <fs...@cloudera.com> wrote:
> Hi Denes,
>
> sounds like a plan, I am more than happy to help, thank you for the
> opportunity.
> I created the umbrella ticket for the release:
> https://issues.apache.org/jira/browse/FLUME-3162
>
> Let me know if any help need.
> Best regards,
> Ferenc Szabo
>
> On Mon, Sep 4, 2017 at 10:21 AM, Denes Arvay <de...@cloudera.com> wrote:
>
> > Hi Flume Community,
> >
> > Almost a year passed since we've released Flume 1.7.
> > More than 50 commits were pushed since then, including documentation
> fixes,
> > many critical bug fixes and several important features, so I'd like to
> > propose to publish the next minor release of Flume.
> >
> > I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> > Marcell Hegedus who have been quite active recently, and Balazs Donat
> > Bessenyei who took the lion's share of the work during the previous
> release
> > - if both community and they are OK with it.
> >
> > Among others the following major changes will be included in the next
> > release:
> >
> > Fixed bugs:
> > - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> > live updating config
> > - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> > count exceeded in MemoryChannel
> > - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> > - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
> to
> > data loss
> > - FLUME-2752. Fix AvroSource startup resource leaks
> > - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> >
> > New features:
> > - FLUME-2171. Add Interceptor to remove headers from event
> > - FLUME-2993. Add support for environment variables in configuration
> files
> > - New component: HTTP Sink
> > - FLUME-3100. Support arbitrary header substitution for topic of Kafka
> Sink
> > - FLUME-2917. Provide netcat UDP source as alternative to TCP
> >
> > There are 35 open tickets targeted for 1.8 in patch available state:
> > https://s.apache.org/flume-1.8-target-tickets
> >
> > Plus we also have quite a lot (~65) open pull requests on GitHub:
> > https://github.com/apache/flume/pulls
> >
> > Some of the above mentioned tickets/pull requests already have some
> review
> > comments, so at least part of this list can get into this release beside
> > the already pushed ones.
> >
> > I'd like to propose to target the week of 11th of September with the
> first
> > release candidate. That'd mean that the branch date would be the 11th,
> any
> > significant code change should get in by that date.
> >
> > If nobody has any concerns then I'm going to create an umbrella ticket to
> > track the release process.
> >
> > Kind regards,
> > Denes
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Miklos Csanady <mi...@cloudera.com>.
Hi Denes,
That's a great idea, I can offer my help in this process.
Regards,
Miklos Csanady
On Fri, Sep 8, 2017 at 9:58 AM, Ferenc Szabo <fs...@cloudera.com> wrote:
> Hi Denes,
>
> sounds like a plan, I am more than happy to help, thank you for the
> opportunity.
> I created the umbrella ticket for the release:
> https://issues.apache.org/jira/browse/FLUME-3162
>
> Let me know if any help need.
> Best regards,
> Ferenc Szabo
>
> On Mon, Sep 4, 2017 at 10:21 AM, Denes Arvay <de...@cloudera.com> wrote:
>
> > Hi Flume Community,
> >
> > Almost a year passed since we've released Flume 1.7.
> > More than 50 commits were pushed since then, including documentation
> fixes,
> > many critical bug fixes and several important features, so I'd like to
> > propose to publish the next minor release of Flume.
> >
> > I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> > Marcell Hegedus who have been quite active recently, and Balazs Donat
> > Bessenyei who took the lion's share of the work during the previous
> release
> > - if both community and they are OK with it.
> >
> > Among others the following major changes will be included in the next
> > release:
> >
> > Fixed bugs:
> > - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> > live updating config
> > - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> > count exceeded in MemoryChannel
> > - FLUME-3020. Improve HDFS Sink escape sequence substitution
> > - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> > - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> > - FLUME-3080. Close failure in HDFS Sink might cause data loss
> > - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
> to
> > data loss
> > - FLUME-2752. Fix AvroSource startup resource leaks
> > - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
> >
> > New features:
> > - FLUME-2171. Add Interceptor to remove headers from event
> > - FLUME-2993. Add support for environment variables in configuration
> files
> > - New component: HTTP Sink
> > - FLUME-3100. Support arbitrary header substitution for topic of Kafka
> Sink
> > - FLUME-2917. Provide netcat UDP source as alternative to TCP
> >
> > There are 35 open tickets targeted for 1.8 in patch available state:
> > https://s.apache.org/flume-1.8-target-tickets
> >
> > Plus we also have quite a lot (~65) open pull requests on GitHub:
> > https://github.com/apache/flume/pulls
> >
> > Some of the above mentioned tickets/pull requests already have some
> review
> > comments, so at least part of this list can get into this release beside
> > the already pushed ones.
> >
> > I'd like to propose to target the week of 11th of September with the
> first
> > release candidate. That'd mean that the branch date would be the 11th,
> any
> > significant code change should get in by that date.
> >
> > If nobody has any concerns then I'm going to create an umbrella ticket to
> > track the release process.
> >
> > Kind regards,
> > Denes
> >
>
Re: [DISCUSS] Flume 1.8 release proposal
Posted by Ferenc Szabo <fs...@cloudera.com>.
Hi Denes,
sounds like a plan, I am more than happy to help, thank you for the
opportunity.
I created the umbrella ticket for the release:
https://issues.apache.org/jira/browse/FLUME-3162
Let me know if any help need.
Best regards,
Ferenc Szabo
On Mon, Sep 4, 2017 at 10:21 AM, Denes Arvay <de...@cloudera.com> wrote:
> Hi Flume Community,
>
> Almost a year passed since we've released Flume 1.7.
> More than 50 commits were pushed since then, including documentation fixes,
> many critical bug fixes and several important features, so I'd like to
> propose to publish the next minor release of Flume.
>
> I'd be happy to be the Release Manager with the help of Ferenc Szabo and
> Marcell Hegedus who have been quite active recently, and Balazs Donat
> Bessenyei who took the lion's share of the work during the previous release
> - if both community and they are OK with it.
>
> Among others the following major changes will be included in the next
> release:
>
> Fixed bugs:
> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
> live updating config
> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
> count exceeded in MemoryChannel
> - FLUME-3020. Improve HDFS Sink escape sequence substitution
> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
> - FLUME-3080. Close failure in HDFS Sink might cause data loss
> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead to
> data loss
> - FLUME-2752. Fix AvroSource startup resource leaks
> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
>
> New features:
> - FLUME-2171. Add Interceptor to remove headers from event
> - FLUME-2993. Add support for environment variables in configuration files
> - New component: HTTP Sink
> - FLUME-3100. Support arbitrary header substitution for topic of Kafka Sink
> - FLUME-2917. Provide netcat UDP source as alternative to TCP
>
> There are 35 open tickets targeted for 1.8 in patch available state:
> https://s.apache.org/flume-1.8-target-tickets
>
> Plus we also have quite a lot (~65) open pull requests on GitHub:
> https://github.com/apache/flume/pulls
>
> Some of the above mentioned tickets/pull requests already have some review
> comments, so at least part of this list can get into this release beside
> the already pushed ones.
>
> I'd like to propose to target the week of 11th of September with the first
> release candidate. That'd mean that the branch date would be the 11th, any
> significant code change should get in by that date.
>
> If nobody has any concerns then I'm going to create an umbrella ticket to
> track the release process.
>
> Kind regards,
> Denes
>