Hi Gents, Cutting for a release is a great idea! I fully agree with Donat's and Mike's comments. Related to Denes's question: I'm in favour of the one-by-one decision and the deadline idea for giving the still open tickets a chance to get resolved. Also I'm here to help with review or patch or any other release related tasks.
Cheers, Attila On Fri, Sep 30, 2016 at 3:13 PM, Denes Arvay <[email protected]> wrote: > Hi Donat, > > Sounds like a great plan, I really like the idea, I'm ok with the release > timeline and you being (co-)RM. > What are your plans regarding to the mentioned 18 issues in patch available > state? Should we decide on a one-by-one basis whether we'd like to include > in the release or should we reschedule all of them to a next release? > I see no blocker issues among them, on the other hand we might want to > include some in the release. > In this case we could set a deadline and the patches having +1/shipit by > the deadline could be included in the release. I'd be happy to help with > prioritization and review. > > What do you think? > > Regards, > Denes > > > > On Fri, Sep 30, 2016 at 12:06 PM Mike Percy <[email protected]> wrote: > > > Hi Donat, > > Thanks for bringing this up again. > > > > +1 on doing a Flume 1.7.0 release right away. It's really long overdue > and > > I don't know of anything that should block the release; I think we met > the > > criteria for having enough improvements to do a release quite a while > ago. > > > > +1 on you being RM or co-RM. I also don't mind helping with the > logistics. > > > > Mike > > > > > > On Fri, Sep 30, 2016 at 9:46 AM, Balazs Donat Bessenyei < > > [email protected] > > > wrote: > > > > > Hi All, > > > > > > We have almost 100 commits since 1.6.0, and a bunch of new features > > > and improvements including a Taildir Source, many upgrades, > > > performance increases, plus a lot of fixes and documentation > > > additions. > > > > > > It seems to me that it's time to cut a 1.7 release soon. I would be > > > happy to volunteer to RM or co-RM the release (possibly together with > > > Lior Zeno who has previously volunteered for such). > > > > > > I know that we have already had a discussion about this. However, as > > > progress seems to have slowed down recently, I suggest re-triaging the > > > tickets to unblock the release and moving forward with the release > > > process right away. > > > > > > Below is the list of tickets that have patches submitted and are > > > scheduled for 1.7.0: > > > https://issues.apache.org/jira/browse/FLUME-2998?jql=project > > > %20%3D%20FLUME%20AND%20status%20%3D%20%22Patch%20Available% > > > > > 22%20AND%20resolution%20%3D%20Unresolved%20AND% > 20fixVersion%20%3D%20v1.7.0 > > > (18 tickets) > > > > > > There are more tickets that have no patch submitted: > > > https://issues.apache.org/jira/browse/FLUME-2998?jql=project > > > %20%3D%20FLUME%20AND%20issuetype%20in%20standardIssueTypes() > > > %20AND%20resolution%20%3D%20Unresolved%20AND% > 20fixVersion%20%3D%20v1.7.0 > > > (30 tickets) > > > > > > I suggest tracking the release process using the JIRA previously filed > > > by Lior at https://issues.apache.org/jira/browse/FLUME-2924 > > > > > > If this all sounds OK, I'd like to suggest targeting the week of > > > October 10 for a first RC. (Also, anything that is non-trivial should > > > get in by October 7. Any feature or big change that is not committed > > > by then would be scheduled for the next release.) > > > > > > That should leave enough time for people to get moving on patches and > > > reviews for their documentation improvements, critical bug fixes, and > > > low-risk enhancements, etc. > > > > > > Also, I would like to propose October 7 (one week from today) for the > > > branch date. > > > > > > Please let me know your thoughts. > > > > > > > > > Best Regards, > > > > > > Donat > > > > > >
