In the "poor code reviews" discussion, Mike Percy suggested opening up a
thread regarding the roadmap for 1.1.0 and beyond, so here's a go at
kicking that off.
I think a the following questions present themselves, along with my
opinions:
- When do we hope to make the next solid release? Do we have a planned
schedule(that I may be unaware of?)
Personally I am not too attached to deciding a date in advance and would
prefer to decide a fixed set of issues that we prioritize to fix, then
limit the branch to bug fixes only(moving any further dev to a separate
branch), and push that out as the next release when sufficient testing
has been made with harmful bugs removed.
- What belongs in 1.1.0?
I for one think that for any log delivery infrastructure the core parts
for delivery mechanisms and error recovery mechanisms should be of
primary importance, and this is what I've been trying to work on. I do
not feel that any further sources or sinks are necessary, but feel that
for delivery mechanisms, the lack of a FileChannel is pretty painful. I
also feel that a buffering mechanism(as in scribed), allowing to store
channel overflow in a long-term medium should be a priority.
I am unsure of configuration overhauls. We have one configuration method
that works. Should a centralized one be an immediate target or one for
1.1.0. Should refactoring the configuration be a priority(it was
pointed out that FlumeConfiguration has become a god class)?
There are a few other leftovers from flume-728: metric collection
infrastructure, documentation, master. Should these be targets for 1.1.0
or for further down the road?
We should probably also make clear which components need to be thread
safe and which don't. We should also verify this is the case.
- Roadmap for v1.1.0 Juhani Connolly
-
