Stable Release Updates types proposal (was Re: Fedora Board Meeting Recap 2010-03-11)

[Jesse Keating]

On Thu, 2010-03-11 at 17:59 -0500, Martin Langhoff wrote:
> On Thu, Mar 11, 2010 at 1:36 PM, Jesse Keating <jkeating at redhat.com> wrote:
> > https://fedoraproject.org/wiki/Stable_Release_Updates_Proposal
> >
> > Here is the link.  I'm going to start a new thread here.
> 
> Thanks for drafting this. Would it make sense to look at the API &
> coupling dimension?
> 
> When a package provides an API/ABI that other software (packaged or
> not!) depends on, the likelyhood of breakage and impact are much
> higher.
> 
> IME, when the update affects a large set of interdependent, tightly
> coupled packages (and external sw) (ie: KDE) the chances of a smooth
> upgrade are vanishingly small, unless you spend QA efforts similar to
> an OS release.
> 
> At the opposite end of the spectrum "Leaf" packages -- (ie: gnote),
> are less likely to break, and less disruptive when it happens.
> 

I had thought about these things, but they didn't strike me as a high
level update type.  And for the leaf node packages, when they do break
it's not as less disruptive as you might think.  Leaf node packages
exist for a reason, they are likely very important to somebody, and if
that breaks, that's going to be a very big issue for that somebody.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20100311/4219e005/attachment.bin