On 03/13/2012 02:17 PM, Ralph Goers wrote:
The only question I have is whether the community considers this release "stable" or "ready
for production" use. If not, I would think using "beta" in the release version would be
helpful. I know that wasn't done for 1.0.0 but I kind of wish it had.
Ralph
I think in its current state if anyone tried to use this in production
they would have some pretty nasty surprises. E.g. reconfiguring a
running agent is still very broken, there are still some thread safety
issues, and not all components are consistent in their behaviors.
On Mar 12, 2012, at 9:59 PM, Arvind Prabhakar wrote:
Hi,
Since the release of version 1.0.0-incubating of Flume, we have made
significant progress in terms of development. Also of significance is
the fact that we have promoted the active development branch to trunk.
We are now technically ready to graduate as a top-level project (TLP).
To ensure that we do not get bogged down by various concerns that
people have expressed in the graduation of other projects, it is
prudent on our part to make a release from the trunk.
For this reason, I am proposing myself to be the release manager for
the upcoming release - version 1.1.0-incubating. The goal of this
release will be to create a distribution from the trunk where all
sources are in the expected org.apache.* namespace. It will also have
significantly more features and bug fixes than the previous release.
I tried earlier to get some discussion kicked off on a roadmap for 1.1.0
to which Mike Percy provided some useful input. What is going in it? Are
we just going to freeze it at the current feature set and fix bugs? Is
Hari's reworking of the configuration going in? Are we going to try and
get a FileChannel implementation in(I personally think this is a pretty
big deal but it seems to have fallen by the wayside). I suppose that a
centralized configuration is not planned for this release then?
In order to bootstrap the process, I will go ahead and create the
release branch right away. If during the discussion on this thread we
feel that the release must contain certain patches not part of this
branch, I will be happy to port them over to the release branch if
they are committed to the trunk.
Thanks,
Arvind Prabhakar
While we have added some cool new features, and fixed some bugs, other
new ones have appeared and some of the sub-tasks of the original
flume-728 task have been left by the wayside. We're talking about
putting 1.1.0 out but there's no target for what 1.1.0 is meant to have?
I hope we're not heading towards a development style of "release
whatever we've done" without a plan.
