What can I say....? I completely agree with you.
Ewan MacMahon wrote:
>> -----Original Message----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Alessandra Forti
>>
>> I believe their main problem is the enormously lengthy procedure to
>> release an rpm in EGEE/LCG.
>>
>>
> Then surely the correct solution is to have a shortcut release process for
> an RPM which is, after all, just a version-bumped copy of one that already
> made it through the process the first time.
>
> And that's without starting in on the merits of sticking to a release process
> that, in the event of this being needed at all, has clearly just released
> something horribly broken to the production repos.
>
>
>> Said that I don't approve at all of this method as it globally screws
>> up sites that update quickly. Now not only the bugged rpm needs to be
>> downgraded by hand but also most of the other rpms involved in the
>> upgrade are out of sync with the current repository and probably will
>> need manual dependencies fiddling.
>>
>>
> As a general rule if it's possible to fix something either:
> - once, centrally,
> - umpteen times on every single affected site,
>
> Then it's better to fix it once, centrally, even if it takes a moderate amount
> of trouble to do so - it's still less effort overall, and is less prone to
> subtle breakage.
>
> Ewan
>
|