On Mon, Sep 29, 2014 at 6:01 AM, Sean Dague <s...@dague.net> wrote:

> On 09/29/2014 05:06 AM, Thierry Carrez wrote:
> > Sean Dague wrote:
> >> Setuptools 6.0 was released Friday night. (Side note: as a service to
> >> others releasing major software bumps on critical python software on a
> >> Friday night should be avoided.)
> >
> > Since it's hard to prevent upstream from releasing over the weekends,
> > could we somehow freeze our PyPI mirrors from Friday noon to Monday noon
> > infra-team time ?
>
> Honestly, I'm not sure that would be very helpful. There tend to be
> people with one eye open on things over the weekend (like I was this
> weekend), and the fact that it was fixed then meant most people never
> saw the break. If we did a giant requirements release every monday
> morning it would also be *far* more difficult to figure out just based
> on release dates which upstream dependency probably just killed us.
>

What about a continuous delay? Like:

- never mirror a package until it's at least 72 hours old
- never mirror a package if it's not the latest release

If a broken release is produced upstream, developers might be able to
detect it before the gate consumes it. Further, if upstream produces a
fixed release within 72 hours, the second rule would mean that infra
doesn't consume the broken one, and will wait until the new one is 72 hours
old (and we don't have to blacklist it in requirements.txt just for our own
sake).


>         -Sean
>
> --
> Sean Dague
> http://dague.net
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to