Sylvain Bauza
ef8335185a
b2acc9fa864b6fe10bc0c5f3786b976b472b1b27 on stable/liberty introduced a sphinx warning which was not treated as an error in stable/liberty nova releasenotes tox runs so it slipped in, but it is treated as an error in master branch nova releasenotes tox runs, and since reno scans the branches, master is broken because of the error in stable/liberty. Plus, reno scans the git history, so right now it's not obvious how to travel back in time and fix the stable/liberty change. This change reduces the level of control we have by not treating reno warnings as errors. This is not fun but it's the only way we can still land release notes until an appropriate fix is merged (in reno or nova). Again, this is a temporary patch and we consider reverting it once bug 1534613 is fixed. Change-Id: Iedb69c66632383e056840e3294a90cda651a8778 Related-Bug: #1534613
OpenStack Nova README ===================== OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs. OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file. Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities. To keep updated with new developments in the OpenStack project follow `@openstack <http://twitter.com/openstack>`_ on Twitter. To learn how to deploy OpenStack Nova, consult the documentation available online at: http://docs.openstack.org For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki: https://wiki.openstack.org/wiki/HypervisorSupportMatrix In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at: http://bugs.launchpad.net/nova Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at: https://git.openstack.org/cgit/openstack/nova Developers should also join the discussion on the mailing list, at: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at: http://docs.openstack.org/developer/nova/ For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file. -- End of broadcast