On Tue, 25 Feb 2014, Thomas D. wrote:
Hi,
Tim Eifler wrote:
This is the release candidate for v8.2.0 stable. It contains a number if
smaller enhancements as well as bug fixes. We plan to release 8.2.0 soon.
On Gentoo we are currently preparing the v7.6 series for our portage
tree [1] (we are waiting for the final fix for issue 35 [2] (and
hopefully 7.6.1) we also experienced while testing).
Now I am reading that 8.2 series will be released soon?
I was looking for a roadmap to understand your release schema. Currently
I am wondering about another new stable release... so it would be nice
if somebody could explain the release schema to me and/or point me to a
roadmap.
Also a recommendation if we should stop working on 7.6 series in favor
of 8.2 series would be nice... I am very sure that we won't add both
versions to our tree until there's a good reason to do so. So we
probably will choose 8.2 if this will become the next GA/recommendation
very soon (ETA will help us to decide).
it boils down to a couple things
1. don't risk destabilizing the existing codebase, if it's a major change to the
internals that could destabilize things, incriment the major
2. it's ready when it's ready. when the major changes are complete and have
"enough" testing, you get the first x.2 release
In the meantime, bugs are reported against the x-1.even release, and minor
enhancements are written (and contributed). eventually the x-1.odd testing
branch needs to be released.
the unfortunante timeing is that 8.2 and 7.6 are going to be released very close
together. unless significant problems are found with 8.2, there will probably
not be another 7.x release.
now, official policy is that only one stable release is supported, but as you
can see from the list, there are still questions about 5.x and earler.
the official recommendation is always to run the latest stable release.
now, all that aside, let's talk practical issues.
8.2 does make significant changes to the module interface, externally developed
modules will need to be modified. Modules that the rsyslog project doesn't have
the ability to test may get modified, but not work.
but other than this internal re-write, the user visible capabilities of 7.6 and
8.2 are going to be pretty similar, and packaging for them should be almost
identical
so my suggestion is to package 7.6, but plan on adding 8.2 as an experimental
package soon. that way people who are less trusting (or who run into trouble)
can use 7.6 and you can get more widespread use of 8.2 for a bit before setting
it so that people will auto-update to it.
does this make sense?
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
