www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez" <car...@apache.org>
Subject Re: Making Policy decisions on artifacts and how they look.
Date Wed, 13 Dec 2006 08:33:29 GMT
On 12/12/06, Steve Loughran <steve.loughran@gmail.com> wrote:
> Carlos, Wendy and others are actually so rigorous about not breaking
> peoples builds they prefer to leave artifacts in the wrong place and
> with bad metadata (eg. commons-logging 1.1.) rather than correct
> obvious defects. That's why we need to lock down the transition of
> artifacts from staging to live. IMO part of the problem is in the
> clients which never invalidate their cache; they assume metadata is
> always complete and perfect. This makes it hard to correct metadata
> bugs because the changes only propagate to new machines.

I think it's a matter of getting people used to it. Nobody thinks
possible that an RPM changes it's dependencies, a new version is
released. In the repo is the same case, just that some projects still
don't care about it and don't help too much.

View raw message