Hi, On 07/25/2015 06:31 PM, Richard Brown wrote:
Hi Peter,
On 25 July 2015 at 16:51, Peter Czanik <peter@czanik.hu> wrote:
It was the default in SLES11. With SLES12 it's not in SLES core any more, but available only through a "legacy" repo. That version is quite old (3.4), already EoL upstream.
My plan is to get the current "factory" version into Leap now, and update both Factory and Leap to syslog-ng 3.7 once released by the end of Summer. This is a version, which syslog-ng upstream can support much longer than anything earlier than syslog-ng 3.6.
From the sound of things, I don't think I need to ask _you_ this question, but for the sake of illustration for anyone else in a similar position to you, I'm still going to ask these 3 questions so everyone knows the sort of things that I think should cross package maintainers minds as they submit things to Leap.
1. Will users get any practical benefit from the new package compared to the version available from SLES?
Yes, there are many. Journal source support, JSON parsing and formatting just to name the most popular from a long list of new features. https://czanik.blogs.balabit.com/2014/10/syslog-ng-3-6-1-is-released/ https://asylum.madhouse-project.org/blog/2013/11/06/syslog-ng-3.5.1/
I think the SLES one, with it's SUSE provided maintenance should still be considered unless there is a compelling reason to upgrade it I personally don't think 'it's old', on it's own, is a valid compelling reason (NOTE: in the case of syslog-ng I realise it's presence in the legacy module means the SUSE provided maintenance may not match what we want for Leap, to me that is a valid compelling reason, but I'm still leaving this question here for everyone else)
Yeah, I already helped out SUSE with a syslog-ng 3.4 bug, that's how I learned about the 'legacy' repo :)
2. Assuming the answer to #1 is Yes, are you comfortable supporting your chosen newer package in Leap for at least a year, preferably with backported patches and not version updates?
Yes.
3. Assuming the answer to #2 is Yes, would you plan to increase the version of the package for Leap 42.2 a year from now?
This is a rather tough question. On one hand I also prefer stability, on the other hand if I learn from feedback, that syslog-ng version 3.X is problematic but 3.Y is all right, I'd rather do the version upgrade. Bye, CzP
Where possible I'd like to see package version choices for Leap favour versions that we can ideally keep around for a while for the sake of long term stability, after all we have Tumbleweed for the 'follow upstream at the pace of upstream' scenario
Regards,
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org