pment List
Subject: Re: EPEL EpSCO Email Meeting:
On 11 September 2014 08:41, Bohuslav Kabrda
mailto:bkab...@redhat.com>> wrote:
Problem trying to be solved:
EPEL's original goal around a 5-7 year product has run into issues where
various packages end up having shorter lifet
On 11 September 2014 08:41, Bohuslav Kabrda wrote:
> Problem trying to be solved:
>
> EPEL's original goal around a 5-7 year product has run into issues where
> various packages end up having shorter lifetimes than can be maintained in
> that period. What happens is that the upstream is changing
> Problem trying to be solved:
> EPEL's original goal around a 5-7 year product has run into issues where
> various packages end up having shorter lifetimes than can be maintained in
> that period. What happens is that the upstream is changing the code too
> massively for any sort of 'back-port' t
On 5 September 2014 12:52, Kevin Fenzi wrote:
> On Thu, 4 Sep 2014 18:20:19 -0600
> Stephen John Smoogen wrote:
>
> > So this is my general proposal for per point release.
> >
> >
> > Problem trying to be solved:
> >
> > EPEL's original goal around a 5-7 year product has run into issues
> > wher
On Thu, 4 Sep 2014 18:20:19 -0600
Stephen John Smoogen wrote:
> So this is my general proposal for per point release.
>
>
> Problem trying to be solved:
>
> EPEL's original goal around a 5-7 year product has run into issues
> where various packages end up having shorter lifetimes than can be
>
On 5 September 2014 08:27, Jeff Sheltren wrote:
> On Fri, Aug 29, 2014 at 3:08 PM, Stephen John Smoogen
> wrote:
>>
>>
>>- EpSCO governance.
>> - Lifetime of initial committee (9 months?)
>>
>> This is fine for me. Somewhere in the 6-12 month range seems reasonable.
>
I am going to t
On Fri, Aug 29, 2014 at 3:08 PM, Stephen John Smoogen
wrote:
>
>
>- EpSCO governance.
> - Lifetime of initial committee (9 months?)
>
> This is fine for me. Somewhere in the 6-12 month range seems reasonable.
>-
> - Replacement of any exiting members (replacement by formal v
On Sep 04 18:20, Stephen John Smoogen wrote:
> So this is my general proposal for per point release.
>
>
> Problem trying to be solved:
>
> EPEL's original goal around a 5-7 year product has run into issues where
> various packages end up having shorter lifetimes than can be maintained in
> that
On 4 September 2014 10:13, Kevin Fenzi wrote:
> On Fri, 29 Aug 2014 16:08:34 -0600
> Stephen John Smoogen wrote:
>
> > So in todays (2014-08-29) meeting, we wanted to move the various
> > policy discussions to email so that people could take their time to
> > reply and also to allow for people w
On 09/05/2014 12:49 AM, Karsten Wade wrote:
For anything related to the new repo, this is an important part of the
idea. We want to set a new expectation with the new brand. Maybe we
can just tie it to the upstream-of-Fedora -- 13 months, rolls with
each Fedora release, etc.?
It would look sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/2014 02:05 PM, Jim Perrin wrote:
> Perhaps this is an issue where a shorter life-cycle expectation
> needs to be set?
For anything related to the new repo, this is an important part of the
idea. We want to set a new expectation with the new b
On 09/04/2014 11:13 AM, Kevin Fenzi wrote:
> On Fri, 29 Aug 2014 16:08:34 -0600
> Stephen John Smoogen wrote:
>
>> So in todays (2014-08-29) meeting, we wanted to move the various
>> policy discussions to email so that people could take their time to
>> reply and also to allow for people who co
On Fri, 29 Aug 2014 16:08:34 -0600
Stephen John Smoogen wrote:
> So in todays (2014-08-29) meeting, we wanted to move the various
> policy discussions to email so that people could take their time to
> reply and also to allow for people who could not attend time to
> respond.
Right.
> Going fr
So in todays (2014-08-29) meeting, we wanted to move the various policy
discussions to email so that people could take their time to reply and also
to allow for people who could not attend time to respond.
Going from the web-page
https://fedoraproject.org/wiki/EPEL-faster-repo-ideas the following
14 matches
Mail list logo