[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Spin Updates Policy Draft



Spin Updates Policy Draft. This  amends my previous Spin Policy Draft.
Nothing in this draft should contradict or conflict with my previous
draft proposal.

1) Release Update Spins are assumed as part of the Release Selection
process by which releng chooses which spins to make part of a Fedora
release and thus provide hosting for.  To estimate space requirements,
every released spin is assumed to consist of a a gold release and an
updated image of maximum size of the target media (cd or dvd and
perhaps bluray), unless the spin maintainer explicitly opts out of
producing updates.  If a spin needs multiple updates in a release,
only the latest update image will be hosted.   The update image must
be named to distinguish it from the hosted gold release image.  The
gold release image will be hosted for the length of the Fedora
Release.

As part of the Release Selection process Spin maintainers may
explicitly state that they will not produce updates, thus lowering the
space requirements for that spin.  Choosing to not produce updates may
influence the decision on the number of spins to release when space is
a constraining factor on the release selection process.

2) All updated spins must re-qualify for the Kickstart Pool through
the same Pre-Approval Testing process outlined in my original draft.
This is true for both hosted Release Update Spins as well as Community
Contributed Spins which make up the kickstart pool.
Any changes in the package set (names not version) should be explained
and covered in the pre-approval process.  Large changes to the
packageset should be avoided as part of an update, but some changes
are easily justified due to package re-naming or splitting.

3)Release Update Spins will not require releng review if they consist
solely of updated packages, with no additional kickstart file changes.

4)Any kickstart file changes in a Release Update Spin trigger a releng
review/approval. A document listing of the reason for each change
should be provided.  ( Hint: good use of bugzilla tickets here for
documenting changes.)

5)update image size can not exceed the estimated maximum for the media
image target (cdrom, dvd, etc).

-jef


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]