I would like to suggest the following plan for Enterprise Extras:
1) There are 4 channels per {Scientific/Centos} Enterprise Linux
extras
extras-devel
extras-testing
extras-updates
[proposed naming convention: extras-2el, extras-3el, extras-4el, extras-5el]
2) Extras are produced/updated on a 6 month basis. Stuff is usually
done in extras-devel but at 5 months a lockdown is done and they are
pushed as being the next dot release (2.1.0,3.1.0,4.1.0,5.1.0 ->
2.2.0,3.2.0,4.2.0,5.2.0)
3) Extras-devel is where development and feature changes are done for
each 6 month lockdown.
4) Extras-testing is where fixes to the current locked down version is
completed before being pushed to extras/extras-updates
5) Extras-updates gets security and fixes to the 'locked' down version
in extras.
So for example:
foo-bar-1.0-1 is put into Extras
foo-bar-1.2-1 is worked on in extras-devel for the next 6 month release
foo-bar-1.0-4 is in Extras-testing to fix a problem in initialization
foo-bar-1.0-2 is in Extras-updates to fix a security problem and will
be replaced with 1.0-4 when it passes testing.
--
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
