I would also say it is important to have a procedure that's easy to
apply. If the newly introduced bug is a serious vulnerability it is not
good to have a difficult process for rolling back, whereby manual
downgrading is needed. I agree it would make sense to use well
established Linux practice.
Linda.
> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Alessandra Forti
> Sent: 26 January 2009 14:03
> To: [log in to unmask]
> Subject: Re: Glite Middleware Rollback proposal.
>
> Hi,
>
> I believe their main problem is the enormously lengthy procedure to
> release an rpm in EGEE/LCG.
>
> 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.
>
> cheers
> alessandra
>
>
> David Grellscheid wrote:
> >> My suggestion of just releasing an higher numbered rpm with the bug
> >> removed was not favoured.
> >>
> >
> > Unbelievable! Did they give a good reason why they don't want to
follow
> > the well-established practice of every Linux distributor?
> >
> > Once again some LCG group decides that other people's experience
counts
> > for nothing when an in-house solution can be cobbled together
instead.
> > I would hope that GridPP tries to take a firm stand on this.
> >
> > See you,
> >
> > David
> >
--
Scanned by iCritical.
|