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
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
