[syslog-ng] cleaning up the unofficial rpm repositories

[Peter Czanik (pczanik)]

Hi,

Thanks for all the feedback. Based on this I only do a partial cleanup now:


  *   delete packages for any end of life Linux distros (Fedora 28 and earlier, openSUSE 15.0 and earlier)
  *   delete packages for rolling releases (Fedora Rawhide, openSUSE Tumbleweed) older than a year

I keep all packages for RHEL/CentOS/SLES now, but plan to clean up that area as well. Lets call that spring cleaning, so we have half a year left 🙂

We have time to discuss until spring, but my current plan is:

  *   keep enterprise (RHEL/SLES) packages for three years
  *   keep regular distro packages until distro is live (1-1.5 years)

I keep creating new repositories for new releases, just as I'm doing now. This seems to be the preferred way, at least according to many personal discussions, as it gives an illusion of LTS, even if older releases normally don't receive fixes.

For those who don't mind occasional bugs and incompatible changes breaking their configurations, I plan to provide a syslog-ng-stable repo, but that will be a separate e-mail.

Bye,

Peter Czanik (CzP) <peter.czanik at oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik

________________________________
From: Peter Czanik (pczanik)
Sent: Thursday, September 5, 2019 9:13 AM
To: syslog-ng at lists.balabit.hu <syslog-ng at lists.balabit.hu>
Subject: cleaning up the unofficial rpm repositories

Hi,

Ever since I started my unofficial rpm packages for (open)SUSE and Fedora/RHEL/CentOS I created a new repository for each new release and never deleted them. Of course OBS and Copr guys did sometimes clean ups, so Fedora and openSUSE packages for long end of life distributions got deleted. But for the rest there are still syslog-ng 3.5 packages on-line.

Not everyone likes to update syslog-ng every second month, so I keep the current workflow and create a new repo for each new release. This way your syslog-ng.conf or package management is not accidentally broken at a random time with a new update, you have a chance to test a new release thoroughly before upgrading. On the other hand I plan to keep only a year worth of releases instead of everything.

Question:


  *   Is there anyone, who needs packages older than one year? With the one year limit I'd delete anything older than 3.17 and delete 3.17 as well, once 3.24 is out, and so on.

Bye,

Peter Czanik (CzP) <peter.czanik at oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190912/b760f451/attachment.html>