Which distributions to support?

--===============2071014559953200692==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="k4f25fnPtRuIRUb3"
Content-Disposition: inline


--k4f25fnPtRuIRUb3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi repo maintainers,

what are your policies on EOLing distributions in your repo? And also
are you seeing any significant use of older distros on your servers?

The support burden, both in specfile exceptions and in infrastructure
setups, has probably reached far beyond the benefits of keeping
backwards compatibility with the added risk of supporting distros w/o
security updates. Recreating the metadata at ATrpms is going into
multiple hours these days (perhaps dumping some metadata formats
should also be considered) ...

Creating a common policy on this and coordinating EOL dates would not
be bad. Factors that should be considered are

o official EOL by vendor
o second tier EOL by organisations like Fedora Legacy or Progeny
o user demand
o infrastructural resources maintainer degradation ;=3D)

Thoughts?
--=20
Axel.Thimm at ATrpms.net

--k4f25fnPtRuIRUb3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCnFbAQBVS1GOamfERAvYgAJ9mjQQjpyLxa7ttDxfy8T5WT9UuVgCbByi7
xwBquomLveJ+jzNV5Dvu0Zw=
=gRIZ
-----END PGP SIGNATURE-----

--k4f25fnPtRuIRUb3--


--===============2071014559953200692==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
repo-coord mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/repo-coord

--===============2071014559953200692==--