On Fri, Apr 23, 2010 at 12:29 PM, Jesse Keating <jkeating(a)redhat.com> wrote:
On Wed, 2010-04-21 at 09:43 -0700, Jesse Keating wrote:
> On Wed, 2010-04-21 at 12:02 -0400, William Jon McCann wrote:
> > 1. Limit the frequency of non-critical updates to once per week in
> > stable releases
> This gets pretty difficult to manage if we want to insert any testing of
> the proposed update set to be pushed out. It increases the number of
> potential push sets, per release, which increases the complexity quite a
> bit in the depchecking routines.
> I'm not saying it's something we shouldn't do, I'm just saying that
> going to make something significantly more complex to manage.
I hate being the "stuff is hard" guy, but I just remembered another
issue with this. Our update classifications have to be carried forward.
That is to say, for a given package foo:
We don't shy away from hard problems if we did we wouldn't be trying
to build a general purpose operating system. So don't worry about it.
Any problem once we define it properly is ultimately solvable.
To help keep track of the various facets to this problem maybe we
should start cataloging them on the wiki. I'm already starting to
lose track in my head.
I've made some space here: