When to move updates from testing to stable

Thorsten Leemhuis fedora at leemhuis.info
Thu Oct 30 10:54:13 CET 2008

On 30.10.2008 10:12, KH KH wrote:
> 2008/10/29 Thorsten Leemhuis <fedora at leemhuis.info>:
>>> Which BTW brings us to the question: how do we want to handle "testing" in
>>> the future?
> Yep and I remember to have asked the same question worded like this:
> Do updates-testing behaviours ends to be like it was with livna or with fedora?

More like Fedora, but not exactly like it as we have no bodhi for now.

>>> The push scripts by default push everything to testing. That is IMHO a
>>> good thing to do as default. But when to move packages to the proper repos?
>>> Simply one week later by default? That would not be that hard to do afaics.
> If the push script default everything to testing, but on the others
> side it lack support for pushing packages to stable. The result is:
> more human admin tasks.

Yeah, that's true. But that's IMHO definitely worth the trouble.

> For example, I want the vlc built in F-9 to be
> pushed to stable right now.

I don't think we should do that. VLC 0.9.5 might have been tested in 
rpmfusion rawhide, but you never know if new problems show up when you 
build a package in a different branch. Hence nearly all updates (except 
kmod and updates that fix important bugs) should get pushed to the 
testing repos and stay there for at least a little while, just like it 
is done in Fedora.

> how should I do ?

Tell me (sorry, that was only indirectly said in the mail you replied 
to, I should have said that directly to make it obvious)

 > [...]
> But what is needed actually is a way to "also" propose an update to
> 0.9.x. Can I handle that with the rpmfusion-free-updates-testing
> repository? It will lead to have two parallels cvs (F-8 F-8.testing
> like it was with livna), because it should remains possible to update
> the two versions.

The F-8 and F-8.testing stuff in livna was a major PITA to maintain for 
me (as the one that was the interface to the buildsys and the one that 
had to keep the repo in shape) in Livna -- especially for kmods, as 
maintainers more then once did crazy things which lead to real problems 
when kmods needed to get built for new Fedora kernels.

It also doesn't work with current CVS/plague design and is afaics not 
that easy to set up (the trick I used in Livna is not possible in CVS 
afaics). So I strongly vote for not even think about things like a 
F-8.testing branch in CVS. Fedora works fine without it as well, so I 
see no real reason why we should need it.


More information about the rpmfusion-developers mailing list