Initial Proposal for doing Enterprise Extras

[Thorsten Leemhuis]

Hi all!

I've waited until now to reply because I've thought about this
suggestion for a while...

smooge, thx for your suggestions!

Stephen John Smoogen schrieb:
> 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]

The idea is nice, but I think this is going to be much to complicated.

> 2) Extras are produced/updated on a 6 month basis.

That might be a nice to have.

> [...]
> 4) Extras-testing is where fixes to the current locked down version is
> completed before being pushed to extras/extras-updates

We IMHO need some kind of extras-testing in the long term.

> [...]

But as I said: I thinks it's to complicated. So I put up the following
up for discussion - it's just and idea, I'm not really sure it it doable
(or worth realizing):

Two devel repos for now:
 * el-devel
 * el-devel-1 (after RHEL5)
 * el4
 * el5

el-devel -> Rolling release scheme for the current version of
{RHEL|CentOS}, repo depends on el{current}. Repo gets into a feature
freeze round about two weeks before each next {RHEL|CentOS} dot release
update (4.4 -> 4.5 or 5.0 -> 5.1) and packages get copied over to the
stable repo when that dot release get's published

el-devel-1 -> Rolling release scheme for the ((current RHEL version)-1)
-- that would be RHEL3 currently (no, we probably don't start building
for RHEL3, it's just to explain the scheme) and will be RHEL4 soon. Same
handling as el-devel. And no, there shouldn't be any el-devel-2 (fixme:
where to test updates later when RHEL6 is out?).

el5 and el4 -> contain the packages for {RHEL|CentOS}{45}. Packages are
locked down there and only get updated for security reasons (after they
were tested or in devel for two (?) days) and on each dot release synced
from devel.

Opinions? Probably to complicated as well...

CU
thl