[packagers] Errata

[Edward Guy Capriolo]

I have no problem with the quality or testing of the package. I know all the packagers do the best job they can. I greatly appreciate their work. I know all the packages are of high quality.

Even if the person committing the package posted a message to this list that would be helpful. It does not need to be a large fancy message/system like the RedHat errata, but I think there is a great benefit to finding a simple organic way to say, "we repacked X to work with product Y." 

It would be a great benefit to the end users. That are asking themselves "Is upgrading this syslinux really worth it?"

Edward

-----Original Message-----
From: packagers-bounces at lists.rpmforge.net [mailto:packagers-bounces at lists.rpmforge.net] On Behalf Of Dag Wieers
Sent: Tuesday, November 27, 2007 5:03 PM
To: Edward Guy Capriolo
Cc: packagers at lists.rpmforge.net
Subject: Re: [packagers] Errata

On Tue, 27 Nov 2007, Edward Guy Capriolo wrote:

> I am not sure this is the right place to suggest this, and I tried to find this information on the rpmforge website but I found nothing.
>
> RedHat maintains errata on all these packages
> https://rhn.redhat.com/errata/rhel-server-errata.html
>
> We have a procedure in place where we run yum check-update every night on our systems. When packages requiring updates appear, we consult the RedHat errata and decide if the need is great to install the packages. (We almost always decide yes but that is not the point)
>
> The important part about the errata is that I find it helpful to know why the package is being updated. The update could be for security, features, or bugs.
>
> Does any similar change log exist for rpmforge? Developer notes etc?

No, we update to the latest version when possible. If you want to know why
you need a newer version, it is up to you to test, check the new version
ChangeLog or whatever you think is necessary.

People may have different reasons for using the latest version, or
sticking with an older version, but we cannot provide the same service as
Red Hat for free for 4x as many packages. That is impossible and we do not
even try to do that :)

Summary: do not use RPMforge packages directly in production without first
testing.

-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
packagers mailing list
packagers at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/packagers