On Tue 22 Apr 2014 07:46:25 AM PDT, Dan wrote:
Hey,
Do you have a roadmap for new releases? There seems to have been quite
a lot of work on dev since 0.5.1 and we were wondering what you plans
were for future releases.
We don't have an extremely rigorous road map, but we do use the github
issue tracker milestones to track what we hope to land in upcoming
versions. All of the issues marked for milestone 0.6
(http://is.gd/azbUSB) are on our wish list for the 0.6 release. We try
to get a new point release out every quarter, and it's not likely that
everything on that milestone will make it in before we actually cut the
0.6 release. When it gets closer to release time we'll create the 0.7
milestone and will start to separate out the items that will be pushed
back.
We prioritize the 0.6 tagged issues based on perceived need. If we have
a strong internal need for a feature, that will of course get priority,
but we also take into account requests that are made and questions that
are asked here on the mailing list and on IRC. If there's an issue in
the tracker that's particularly dear to you, feel free to comment on it
so we know that the demand is out there.
Note that so far I've been talking about full point releases, which
contain new features and documented backwards incompatibilities. Much
sooner than 0.6 will be a 0.5.2 release which will include bug fixes
that have landed on the versions/0.5 branch since 0.5.1 was released.
We are looking at using the apache decoder but that seems to depend on
current dev given refactoring work. We're testing it with the latest
dev at the moment.
What release are mozilla using, is it closer to dev?
In Mozilla we typically use the latest release until such time as a
particular instance has a need for a feature that hasn't yet been
released. It hasn't been very long since the 0.5 release, so most of
our installs are currently on 0.5.1. As time goes by and more
compelling stuff lands on dev, however, more of our internal deploys
will be updated to a more recent snapshot. Immediately before 0.5's
release most of our installs were using a snapshot b/c they needed the
newer features. I expect the same will be true as we get closer to 0.6.
Not ideal perhaps, but it's part of what happens when you're tracking
young software. As Heka matures and things start changing more slowly,
w/ fewer breaking changes, I imagine we'll end up sticking to releases
much more.
Hope this helps!
-r
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
