[
https://issues.apache.org/jira/browse/FLUME-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197130#comment-13197130
]
Arvind Prabhakar commented on FLUME-922:
----------------------------------------
Hi Bruno,
There seems to be strong interest in flume-728's next maintenance release
1.1.0-incubating. We are working to make it feature rich and give it the
necessary stability and functionality to make it worthy of production
environments. Hence, I suggest that for the moment we continue to keep
development separated out as it currently is - with trunk maintaining the
0.9.4+ version and the flume-728 maintaining the 1.1.X version.
Once we are past the version 1.1.0-incubating, we can revisit this issue.
Thanks,
Arvind
> Straighten up branches for development
> --------------------------------------
>
> Key: FLUME-922
> URL: https://issues.apache.org/jira/browse/FLUME-922
> Project: Flume
> Issue Type: Improvement
> Components: Technical Debt
> Reporter: Bruno Mahé
>
> FLUME-728 was very useful when developing Flume 1.0.0, but now it's quite
> confusing to do post 1.0.0 development on a FLUME-728 branch, while 0.9.X is
> done on trunk.
> So this ticket is about figuring out the best way to go forward.
> Here are some questions:
> * Is there going to be maintenance release of 1.1.X or is it unnecessary
> given that Flume 1.X is still qualified as alpha quality by its community?
> * Will most of the development happen on the FLUME-728 (or whatever new name,
> if needed) or is there a need for a separate branch for trunk / 1.X / 1.0.X?
> Note: I can also volunteer on doing some of the work
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
