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
