openstack/openstack-helm
Code Issues Proposed changes

Updates Launchpad references to Storyboard

Browse Source 
Updates references to Launchpad to now point to Storyboard, since OSH has
migrated to that platform.  "Report a bug" type references are updated to
point straight to the OSH project proper in Storyboard, while general backlog
type references are updated to point to the OSH Project Group.

Change-Id: I63e290f34763847e71e14e4471e7ee9460d8cff9
Task: 21684
Story: 2002199
This commit is contained in:
mattmceuen 2018-06-09 19:34:06 -05:00
parent 7051db7c81
commit 602358403d
6 changed files with 17 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.rst
View File

@ -11,6 +11,6 @@ https://docs.openstack.org/infra/manual/developers.html#development-workflow
Pull requests submitted through GitHub will be ignored. Pull requests submitted through GitHub will be ignored.
Bugs should be filed on Launchpad, not GitHub: Bugs should be filed as stories in Storyboard, not GitHub:
https://bugs.launchpad.net/openstack-helm https://storyboard.openstack.org/#!/project/886

11
README.rst
View File

@ -20,13 +20,10 @@ Communication
* Meeting Agenda Items: `Agenda * Meeting Agenda Items: `Agenda
<https://etherpad.openstack.org/p/openstack-helm-meeting-agenda>`_ <https://etherpad.openstack.org/p/openstack-helm-meeting-agenda>`_
Launchpad Storyboard
--------- ----------
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://storyboard.openstack.org/#!/project_group/64>`_.
* `Bugs <https://bugs.launchpad.net/openstack-helm>`_
* `Blueprints <https://blueprints.launchpad.net/openstack-helm>`_
Installation and Development Installation and Development
---------------------------- ----------------------------
@ -39,7 +36,7 @@ up can be found `here <https://docs.openstack.org/openstack-helm/latest/install/
This project is under active development. We encourage anyone interested in This project is under active development. We encourage anyone interested in
OpenStack-Helm to review our `Installation <https://docs.openstack.org/openstack-helm/latest/install/index.html>`_ OpenStack-Helm to review our `Installation <https://docs.openstack.org/openstack-helm/latest/install/index.html>`_
documentation. Feel free to ask questions or check out our current documentation. Feel free to ask questions or check out our current
`Issues and Bugs <https://bugs.launchpad.net/openstack-helm>`_. `Storyboard backlog <https://storyboard.openstack.org/#!/project_group/64>`_.
To evaluate a multinode installation, follow the To evaluate a multinode installation, follow the
`Bare Metal <https://docs.openstack.org/openstack-helm/latest/install/multinode.html>`_ `Bare Metal <https://docs.openstack.org/openstack-helm/latest/install/multinode.html>`_

6
doc/source/install/multinode.rst
View File

@ -13,9 +13,9 @@ such as MariaDB (Galera). Although we assume that the project should
provide a "batteries included" approach towards persistent storage, we provide a "batteries included" approach towards persistent storage, we
want to allow operators to define their own solution as well. Examples want to allow operators to define their own solution as well. Examples
of this work will be documented in another section, however evidence of of this work will be documented in another section, however evidence of
this is found throughout the project. If you have any questions or this is found throughout the project. If you find any issues or gaps,
comments, please create an `issue please create a `story <https://storyboard.openstack.org/#!/project/886>`_
<https://bugs.launchpad.net/openstack-helm>`_. to track what can be done to improve our documentation.
.. note:: .. note::
Please see the supported application versions outlined in the Please see the supported application versions outlined in the

6
doc/source/specs/specifications.rst
View File

@ -21,13 +21,13 @@ drafted and approved.
Process Process
------- -------
Before drafting a specification, a blueprint should be filed in Launchpad_ along Before drafting a specification, a blueprint should be filed in Storyboard_
with any dependencies the blueprint requires. Once the blueprint has been along with any dependencies the blueprint requires. Once the blueprint has been
registered, submit the specification as a patch set to the specs/ directory registered, submit the specification as a patch set to the specs/ directory
using the supplied template. using the supplied template.
More information about the blueprint + specification lifecycle can be found More information about the blueprint + specification lifecycle can be found
here_. here_.
.. _Launchpad: https://blueprints.launchpad.net/openstack-helm .. _Storyboard: https://storyboard.openstack.org/#!/project_group/64
.. _here: https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs .. _here: https://wiki.openstack.org/wiki/Blueprints#Blueprints_and_Specs

6
doc/source/specs/template.rst
View File

@ -10,9 +10,9 @@
Blueprint Title Blueprint Title
=============== ===============
Include the URL of your Launchpad blueprint: Include the URL of your Storyboard RFE:
https://blueprints.launchpad.net/openstack-helm/+spec/example https://storyboard.openstack.org/#!/story/1234567
Problem Description Problem Description
=================== ===================
@ -51,7 +51,7 @@ Who is leading the implementation?
Designate the primary author and contact. Designate the primary author and contact.
Primary assignee: Primary assignee:
<launchpad-id or None> <Gerrit Id or None>
Work Items Work Items
---------- ----------

4
doc/source/troubleshooting/index.rst
View File

@ -25,5 +25,5 @@ Channels
Bugs and Feature requests Bugs and Feature requests
------------------------- -------------------------
When discovering a new bug, please create a new issue in `Launchpad When discovering a new bug, please report a bug in `Storyboard
<https://bugs.launchpad.net/openstack-helm>`_. <https://storyboard.openstack.org/#!/project/886>`_.