Pushing updates for Fedora 7

[Thorsten Leemhuis]

/me really thinks the subject is bad and confusing; some people seem to
talk about "Pushing updates for existing packages through
update-testing" (as the subject could indicate) other about "Pushing new
packages through updates-testing first"; hopefully most differentiate...

On 01.06.2007 18:00, Bastien Nocera wrote:
> On Fri, 2007-06-01 at 15:10 +0200, Thorsten Leemhuis wrote:
>> On 01.06.2007 14:43, Josh Boyer wrote:
>>> On Fri, 2007-06-01 at 14:24 +0200, Hans de Goede wrote:
>>>> 1) Can it cause regressions for existing users? -> No
>>> It can cause new problems.
>> +1
>>>> 2) Will it get installed automatically by the relative few people who have 
>>>> updates -testing enabled, and thus see any kind of testing (atleast if its 
>>>> installable)? -> No
>>> You're making an assumption that there are few people that enable
>>> updates-testing.
>> /me has it enabled on nearly all of his machines and that way prevented
>> at least once or twice in the past that bad updates hit updates-proper
> How often do you install new packages from updates-testing?

Until now there were nearly never new packages in update-testing as only
Core had updates-testing -- but Core rarely had new packages so the repo
was only used for updates normally. So the answer until now is: Never,
or only, if the new package was tracked in by a dep.

> I use updates-testing just like a lot of other people, but I've never
> installed new packages from it, I don't even know how to see which new
> packages are available there without listing the directory.

See above. But I assume soon you'll see update-testing announcements on
fedora-test-list just as we did in the past for update. If it's
something I might be interested in I'd in the future say "hey, that apps
sounds cool; I give it a quick try just to know if it really is". There
are small chances I find a bug while at it. If it's not a bad bug: yeah,
push the package over to updates-proper and deal with it later.

> [...]

Cu
thl