Hi,
This email has important information for folks who are building Heka
from source, tracking the latest developments on the dev branch. If this
is not you, you can stop reading now.
A bit ago I warned about significant incoming changes as the
router_buffering branch was going to be merged to the dev branch. Since
then, however, I've realized that it will be necessary to maintain
parallel branches for a brief time, so bugs can be fixed against the
more stable, non-router-buffering code, which is in production use by
Mozilla, while still allowing the router-buffering code to be tested and
improved until it's ready to be deployed.
My current plan, then, is to cut a versions/0.10 branch, which will
eventually lead to the v0.10.0 release. The versions/0.10 branch will
get the router buffering merged in, so it can be used by folks who are
writing plugins against the new API, or who want to help test out the
bleeding edge.
Then I'm going to remove the router buffering code from the dev branch,
so folks who might be tracking dev, but aren't yet ready to take the
plunge into the bigger changes that the router buffering introduces, can
continue to track dev. Eventually router buffering *will* be merged back
to dev, of course, but this won't happen until it's seen a bit more
testing, and we're reasonably confident that it can be deployed without
causing major instability or performance issues.
I'm going to get this all taken care of as soon as this email goes out.
Hopefully this makes sense to everyone. If not, please feel free to ask
questions either by replying here on the list or by popping in to the
#heka channel on irc.mozilla.org.
Thanks!
-r
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
