Open Stack

Excerpts from Andreas Jaeger's message of 2017-02-10 13:57:03 +0100:
> On 02/08/2017 05:22 PM, Jay Faulkner  wrote:
>  > [...]
> > IMO, I’d suggest skipping this and just fixing the broken attribute. Projects that are impacted by the change simply need to merge a one-line change to set warnerrors=false. FWIW, you can actually run a local docs build, find and resolve warnings without the PBR change. It seems overkill to me to change the term since doing so will be super confusing to anyone who hasn’t read this mailing list thread.
> >
> > If there’s a significant enough concern, a change could be pushed to set warnerrors=false on the projects that are concerned before this release is made.
> 
> Yes, this should indeed be an easy change to fix it.
> 
> So, since requirements freeze is over, let me remove my WIP on
> https://review.openstack.org/430618 so that it can be released as 
> convenient for the release team,
> 
> Andreas

I think we're unlikely to release a new version of pbr until after the
ocata final releases are done. It's too pervasive and poses a lot of
risk if something is broken.

Doug