On Wed, Nov 21, 2012 at 11:21 AM, Stephen John Smoogen <smo...@gmail.com> wrote: > OK from the various problems with various packages and the needs of > packaging groups for a faster place for development and users for a > more stable and knowing release cycle.. I would like to open the floor > to what we can do to make EPEL more useful to both groups as best as > possible with the goal that the proposals are finalized by FUDcon > Lawrence and work on them completed within 6 months. > > 1) Formalize what EPEL does and how it does it. > - Who gets to decide about updates > - How do we update major items (regularly after a RHEL release? after > a Fedora release?) > - How do we say "we can't support this architecture/release" anymore? > 2) Make sure it is documented what the Fedora Build System can do for > us and what it can't. > - Repotags (yes/no) > - Multiple channels for devel, testing, stable, old (yes/no)? > - Building for PPC/etc architectures when we don't have systems anymore? >
I'd love to be a part of this discussion, but I won't be at the FUDcon. I'd be happy to block time on calendars and such to attend/discuss remotely. Mike > -- > Stephen J Smoogen. > "Don't derail a useful feature for the 99% because you're not in it." > Linus Torvalds > "Years ago my mother used to say to me,... Elwood, you must be oh > so smart or oh so pleasant. Well, for years I was smart. I > recommend pleasant. You may quote me." —James Stewart as Elwood P. Dowd > > _______________________________________________ > epel-devel-list mailing list > epel-devel-list@redhat.com > https://www.redhat.com/mailman/listinfo/epel-devel-list _______________________________________________ epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list