On Mon, Oct 26, 2015 at 2:44 PM, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 26.10.2015 um 14:30 schrieb Michael Melcher:
On Mon, Oct 26, 2015 at 1:54 PM, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
The current version of squid in Leap is provided by SLE12. -> this means; it is maintained by SUSE in the enterprise space which means at least something
Since Leap was pulled from SLE it could mean two things: 1: There actually is a reason to Keep the Version from SLE or 2: nobody bothered yet to upgrade it yet.
Yes, absolutely correct. I cannot answer that question as well. The openSUSE squid maintainer probably knows.
I already contacted them. Lets see if they join the discussion here on the ML.
This is always the case. And in one month the version we included is again outdated. In 95 out of 100 version updates you find bugs fixed and still we have to freeze.
Right, thats why SUSE / openSUSE do backports of important bug/security fixes.
Let's break down the above question to a few more related ones: - is an update worth the effort to transfer maintenance work from SUSE to openSUSE?
Depends on the backporting status of the bug and security fixes. But that the 3 Maintainers can eventually answer better than me.
- would you step up to maintain squid in Leap 42 and do the additional maintenance work?
I'm afraid I'm too new with Suse. I'm willing to though. I'll have a lot to learn regarding the build and maintenance process of *SUSE.
- is it important to keep some kind of compatibility for squid on SLE12 and Leap 42?
That could be answered by the maintainers eventually too.
I have an opinion about all these questions. Depending on your arguments the decision could be changed (apart from the fact that it's basically too late for 42.1 but can be readdressed with 42.2).
Kind regards Michael -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org