On Mon, Oct 18, 2010 at 12:28:23PM -0500, Michael Stahnke wrote:
>
> I wondered if we should attempt to mirror what Red Hat does with its
> support for the enterprise product line.

My understanding was that (and since EPEL beginning) we tried to
mimic what Red Hat does. With the obvious caveat that there is no
contract binding us.

--
Pat

_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list

On Monday, October 18, 2010 12:28:23 pm Michael Stahnke wrote:
> During our weekly EPEL discussion of bugs, some conversation started
> around EL4. We realize there is still a significant EL4 population
> out in the wild, but at the same time many of the open bugs are not
> fixable, or not easily fixable given the versions of software
> available.
>
> I wondered if we should attempt to mirror what Red Hat does with its
> support for the enterprise product line. The following link describes
> how Red Hat handles support through the release cycle (7 years of
> support) for a version of RHEL. While EPEL may not want to mirror
> exactly date-for-date, this might be a good baseline to look at when
> considering how to handle bugs on older version of EL and EPEL.
>
> I'd like to have much more discussion on this topic from package
> maintainers, bug fixers, and from EPEL users.
>
> If you'd like to chime in, please do.
>
> https://access.redhat.com/support/policy/updates/errata/
>
> stahnma

I thought it was long ago decided that once a RHEL release hits the point of
maintainece only epel would do the same.

however it could all be just in my head

Dennis
_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list