Hi all,
a question on the forum
(http://www.rsyslog.com/PNphpBB2-viewtopic-p-1113.phtml#1113 ) and a bit
asking around finally made me think about the possibility of a v3 stable
version, something that dangled on my mind for a while now... While it
is just three month since v2 stable, we have gone a long way and during
that time the new queue engine has much matured. As "development" state
is most often a show-stopper for putting code into production, I think
about releasing a 3.0.0 stable (based on the most recent 3.12.x version
WITHOUT RELP support).
From a support perspective, I'd like to continue support v2 stable and
obviously v3 stable and development concurrently. Development would
continue with 3.13.0 (RELP support), and 3.0.0 would only receive bug
fixes. Some time from now, 3.<whatever>.<whatever> would become 3.1.0
stable. At this point, I would drop support/fixing for 3.0.<whatever>
and ask users with problems in the branch to update to 3.1.<whatever>.
Does this sound reasonable? The big problem is that I must be careful
not to create too many version which I must support, but at the same
time allow new, matured, features to go into broader production. And, of
course, 3.0.0 stable would probably be a bit less stable than 2.0.4, but
only if you use features that are not present in v2. All in all, the
queue engine has received more than a fire drill and is ready for
production - though probably not fully trouble free. But we won't see
that until it gets more used.
Feedback is appreciated.
Thanks,
Rainer
a question on the forum
(http://www.rsyslog.com/PNphpBB2-viewtopic-p-1113.phtml#1113 ) and a bit
asking around finally made me think about the possibility of a v3 stable
version, something that dangled on my mind for a while now... While it
is just three month since v2 stable, we have gone a long way and during
that time the new queue engine has much matured. As "development" state
is most often a show-stopper for putting code into production, I think
about releasing a 3.0.0 stable (based on the most recent 3.12.x version
WITHOUT RELP support).
From a support perspective, I'd like to continue support v2 stable and
obviously v3 stable and development concurrently. Development would
continue with 3.13.0 (RELP support), and 3.0.0 would only receive bug
fixes. Some time from now, 3.<whatever>.<whatever> would become 3.1.0
stable. At this point, I would drop support/fixing for 3.0.<whatever>
and ask users with problems in the branch to update to 3.1.<whatever>.
Does this sound reasonable? The big problem is that I must be careful
not to create too many version which I must support, but at the same
time allow new, matured, features to go into broader production. And, of
course, 3.0.0 stable would probably be a bit less stable than 2.0.4, but
only if you use features that are not present in v2. All in all, the
queue engine has received more than a fire drill and is ready for
production - though probably not fully trouble free. But we won't see
that until it gets more used.
Feedback is appreciated.
Thanks,
Rainer