[opensuse-factory] Version Bump for Squid in Leap
Hi, would it be possible to get the version of Squid bumped up to what upstream suggests as stable?
From squid-cache.org: Version | Latest Release 4.0 | 14 Oct 2015 | 4.0.1 3.5 | 01 Oct 2015 | 3.5.10
The current Version in Leap is 3.3.13-1.2, which was released before May 2015. squid-cache.org says: Old Versions: Provided for archival purposes only. Not intended for general use in new installations. Version | First STABLE release Date | Latest Release | Latest Release Date 3.4 | 09 Dec 2013 | 3.4.14 | 01 Aug 2015 3.3 | 09 Feb 2013 | 3.3.14 | 01 May 2015 Kind regards Michael Melcher -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 26.10.2015 um 13:39 schrieb Michael Melcher:
would it be possible to get the version of Squid bumped up to what upstream suggests as stable?
From squid-cache.org: Version | Latest Release 4.0 | 14 Oct 2015 | 4.0.1 3.5 | 01 Oct 2015 | 3.5.10
The current Version in Leap is 3.3.13-1.2, which was released before May 2015.
I'm not involved really in squid but some general remarks: 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 Now the usual questions to be answered are: - which advantages does an update have? ("a newer version is available" is probably not enough of an argument) - which version is in Factory? (3.5.10; this would fit your expectation) - will the openSUSE community do the maintenance for 3.5.10 for the Leap lifetime? (for this asking on the mailing list only helps partially) -> first approach would be to ask the openSUSE maintainer: osc maintainer -e openSUSE:Factory squid what he thinks about it and depending on the answer more discussions might be required. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 26 of October 2015 13:54:37 Wolfgang Rosenauer wrote:
Am 26.10.2015 um 13:39 schrieb Michael Melcher:
would it be possible to get the version of Squid bumped up to what
upstream suggests as stable?
From squid-cache.org: Version | Latest Release 4.0 | 14 Oct 2015 | 4.0.1 3.5 | 01 Oct 2015 | 3.5.10
The current Version in Leap is 3.3.13-1.2, which was released before May 2015. I'm not involved really in squid but some general remarks: ...
Neither am I. One more general remark, though: we have a Release Candidate out and 4 days before (planned) Gold Master. I don't think this is a good time for a version upgrade request. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Oct 26, 2015 at 1:54 PM, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 26.10.2015 um 13:39 schrieb Michael Melcher:
would it be possible to get the version of Squid bumped up to what upstream suggests as stable?
From squid-cache.org: Version | Latest Release 4.0 | 14 Oct 2015 | 4.0.1 3.5 | 01 Oct 2015 | 3.5.10
The current Version in Leap is 3.3.13-1.2, which was released before May 2015.
I'm not involved really in squid but some general remarks:
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.
Now the usual questions to be answered are: - which advantages does an update have? ("a newer version is available" is probably not enough of an argument)
New Versions usually bring bug fixes and security fixes. Aside from that, the Squid Team itself suggests upgrading.
From The Freenode IRC Channel: * Topic for #squid is: Don't ask to ask, just ask and wait. PasteBin squid.conf if need be. | Or try http://wiki.squid-cache.org/SquidFaq | http://workaround.org/f=squid | Please upgrade to Squid-3.5.10 or 4.0.1 beta
The ChangeLog (which seems to be an actual Code Diff is about 973 lines Long: http://www.squid-cache.org/Versions/v3/3.5/squid-3.5.10.patch The first 30 lines of the Change Log are good enough a reason for me to request an upgrade :-)
- which version is in Factory? (3.5.10; this would fit your expectation)
3.5.10 would be good. Perhaps the Squid Package could be split into squid3 and squid4 to provide both Versions.
- will the openSUSE community do the maintenance for 3.5.10 for the Leap lifetime? (for this asking on the mailing list only helps partially)
If not on the Mailing list, where else?
-> first approach would be to ask the openSUSE maintainer: osc maintainer -e openSUSE:Factory squid what he thinks about it and depending on the answer more discussions might be required.
I'll ask them. Thanks for your quick Feedback. Michael -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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.
Now the usual questions to be answered are: - which advantages does an update have? ("a newer version is available" is probably not enough of an argument)
New Versions usually bring bug fixes and security fixes. Aside from that, the Squid Team itself suggests upgrading. From The Freenode IRC Channel: * Topic for #squid is: Don't ask to ask, just ask and wait. PasteBin squid.conf if need be. | Or try http://wiki.squid-cache.org/SquidFaq | http://workaround.org/f=squid | Please upgrade to Squid-3.5.10 or 4.0.1 beta
The ChangeLog (which seems to be an actual Code Diff is about 973 lines Long: http://www.squid-cache.org/Versions/v3/3.5/squid-3.5.10.patch The first 30 lines of the Change Log are good enough a reason for me to request an upgrade :-)
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. 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? - would you step up to maintain squid in Leap 42 and do the additional maintenance work? - is it important to keep some kind of compatibility for squid on SLE12 and Leap 42? 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).
- will the openSUSE community do the maintenance for 3.5.10 for the Leap lifetime? (for this asking on the mailing list only helps partially)
If not on the Mailing list, where else?
as I said. Asking the maintainer ...
-> first approach would be to ask the openSUSE maintainer: osc maintainer -e openSUSE:Factory squid what he thinks about it and depending on the answer more discussions might be required.
I'll ask them.
yes, the right thing to do and I'll shut up now since squid is really not my topic. I just wanted to explain possible reasoning and ways how to handle these type of requests. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
On Monday 26 of October 2015 14:30:22 Michael Melcher wrote:
New Versions usually bring bug fixes and security fixes.
...and new bugs. Funny how people tend to forget about that. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Michael Melcher -
Michal Kubecek -
Wolfgang Rosenauer