On Thu, Dec 10, 2009 at 5:15 PM, Kevin Fenzi <[email protected]> wrote: > I would like to look at doing something a bit different for tomorrows > EPEL meeting that will take place in #fedora-meeting on > irc.freenode.net at 21:00 UTC. > > We don't have many topics on the agenda, so how about either: > > a) Using the time to try and triage EPEL bugs, and/or fix/close some > low hanging fruit/easy fix bugs. > > or > > b) Introduce how things work in EPEL and help any new folks that are > interested in joining up or branching and building their packages for > EPEL. > > Thoughts? > > A or B ? or Just have a regular meeting and go over any specific topics > people come up with? > > kevin > > _______________________________________________ > epel-devel-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/epel-devel-list > > Probably not the best topic as it's been beaten a bit, but can we update some stuff? If it's a non ABI/API breakage, can I update a package to add new features/fix bugs (not security related)?
I am kind of unclear on this policy. Lately it feels like we opted for "no updates" because it was easy, and not always what users/customers want/need. Thoughts? stahnma _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
