It would be nice to target a v5 version of rsyslog for stablization. Current stable is quite old, and 5.x has been working quite nicely on my machines. It seems specifically, that 5.6.4 has only been in the tree for a few weeks, however the 5.6 series in general has been progressing nicely, so it seems to be a good target. Reproducible: Always
Maybe it's a good idea to not immediately drop old versions, or you will never have one long enough (30 days is the usual) in the tree to call for stabilisation: # ChangeLog for app-admin/rsyslog # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/app-admin/rsyslog/ChangeLog,v 1.36 2011/03/04 09:01:47 ultrabug Exp $ *rsyslog-5.6.4 (04 Mar 2011) 04 Mar 2011; Ultrabug <ultrabug@gentoo.org> -rsyslog-5.6.3.ebuild, +rsyslog-5.6.4.ebuild: version bump. drop old. *rsyslog-5.6.3 (07 Feb 2011) 07 Feb 2011; Ultrabug <ultrabug@gentoo.org> -rsyslog-5.6.2.ebuild, +rsyslog-5.6.3.ebuild: Version bump, drop old
But stabilizing a version with known bugs is not really an option as well.
Yeah, I was kinda curious if maybe the 5.6 series in general was good for stabilization; while 5.6.4 hasn't met the 30-day mark specifically, the new series has been moving nicely through ~arch.
FYI all, I just bumped the new 5.6.5 version. @Jeroen : for the principle, I sure agree with you. Thing is that I "took over" the maintainship of the package few months ago only and I prefered having the ~arch versions rolling for a while before thinking stabilization. I also have to agree with Tiziano on being careful with stabilizing known bugged versions but we all agree that this applies to most of the other packages too. @Andrew : I'm using it on 10+ log-heavy production servers since 5.6.2 version and it just works perfect. So I think we should indeed consider stabilizing the 5.6.4 when it reaches the 30 days flag (in 10 days, yay) since the 3.x series are just not developed anymore. @Tiziano : I'll ping you on IRC so we can talk and decide about this plz
(In reply to comment #4) > FYI all, I just bumped the new 5.6.5 version. > > @Jeroen : for the principle, I sure agree with you. Thing is that I "took over" > the maintainship of the package few months ago only and I prefered having the > ~arch versions rolling for a while before thinking stabilization. I also have > to agree with Tiziano on being careful with stabilizing known bugged versions > but we all agree that this applies to most of the other packages too. > > @Andrew : I'm using it on 10+ log-heavy production servers since 5.6.2 version > and it just works perfect. So I think we should indeed consider stabilizing the > 5.6.4 when it reaches the 30 days flag (in 10 days, yay) since the 3.x series > are just not developed anymore. Sounds like a plan, let's go for it.
Time to roll in the stable phase, please arches let's stabilize app-admin/rsyslog-5.6.4 Thanks
amd64 stable
x86 stable. Thanks.
Stable for HPPA.
Thanks everyone, closing here :)