Migrate back to launchpad

Change-Id: I07b19f630e60590cc7f5d9c0cc18ebde2512f67c
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>

CONTRIBUTING.rst

@@ -19,9 +19,9 @@ the workflow documented at:
 
 (Pull requests submitted through GitHub will be ignored.)
 
-Bugs should be filed on Storyboard now, not GitHub:
+Bugs should be filed on Launchpad now, not GitHub:
 
-   https://storyboard.openstack.org/#!/project/openstack/trove
+   https://bugs.launchpad.net/trove
 
 We welcome all types of contributions, from blueprint designs to
 documentation to testing to deployment scripts. The best way to get
@@ -171,17 +171,14 @@ process.
    there is no available volunteer who will step up to take over the
    patch set.
 
-Storyboard Bugs
----------------
+Launchpad Bugs
+--------------
 
-Bugs should be filed on Storyboard at:
+Bugs should be filed on Launchpad at:
 
-    https://storyboard.openstack.org/#!/project/openstack/trove
+    https://bugs.launchpad.net/trove
 
-All changes that address a Storyboard bug should include the bug in the
-Commit Message using the Story and Task.
-
-It is not required that a Storyboard bug be filed for every change.
+It is not required that a Launchpad bug be filed for every change.
 
 Release Notes
 -------------
@@ -192,7 +189,7 @@ that are submitted as part of a change will be included in the release
 notes. The failure to add a release note for a user visible change
 should be identified in review, and corrected.
 
-If a Storyboard bug is being fixed, the release note should list the
+If a Launchpad bug is being fixed, the release note should list the
 story and task number.
 
 For help using reno, the release notes tool, see:
@@ -258,13 +255,12 @@ following on your development system and ensure that they pass.
 .. code-block:: bash
 
     $ tox -e pep8
-    $ tox -e py39
+    $ tox -e py311
     $ tox -e pylint
 
 If you are unable to get these to pass locally, it is a waste of the
 CI resources to push up a change for review.
 
-
 Testing
 =======
 
@@ -293,11 +289,11 @@ To run all tests and PEP8, run tox, like so:
 
     $ tox
 
-To run just the tests for Python 3.9, run:
+To run just the tests for Python 3.11, run:
 
 .. code-block:: bash
 
-    $ tox -epy39
+    $ tox -epy311
 
 To run just PEP8, run:
 
@@ -328,4 +324,3 @@ Is there something missing?
 
 Do not hesitate to chat and clear your doubts about Trove in
 IRC: #openstack-trove on OFTC.
-

README.rst

@@ -4,8 +4,6 @@ Trove
 
 .. image:: https://governance.openstack.org/tc/badges/trove.svg
 
-.. Change things from this point on
-
 Trove is Database as a Service for OpenStack.
 
 Getting Started
@@ -25,7 +23,7 @@ CONTRIBUTING.rst_ and HACKING.rst_
 * `Developer Docs <https://docs.openstack.org/trove/latest/>`_
 
 You can raise bugs here:
-`Bug Tracker <https://storyboard.openstack.org/#!/project/openstack/trove>`_
+`Bug Tracker <https://bugs.launchpad.net/trove>`_
 
 The plan for trove can be found at
 `Trove Specs <https://specs.openstack.org/openstack/trove-specs/>`_

api-ref/source/conf.py

@@ -35,9 +35,8 @@ html_theme_options = {
     "sidebar_mode": "toc",
 }
 openstackdocs_repo_name = 'openstack/trove'
-openstack_auto_name = False
 openstackdocs_bug_project = 'trove'
-openstackdocs_bug_tag = ''
+openstackdocs_bug_tag = 'docs'
 
 # If extensions (or modules to document with autodoc) are in another directory,
 # add these directories to sys.path here. If the directory is relative to the

backup/Dockerfile

@@ -1,6 +1,6 @@
 ARG BASE_OS_VERSION=24.04
 FROM quay.io/openstack.trove/ubuntu:$BASE_OS_VERSION
-LABEL maintainer="Trove Project (https://storyboard.openstack.org/#!/project/openstack/trove)"
+LABEL maintainer="Trove Project (https://launchpad.net/trove)"
 
 ARG DATASTORE="mysql"
 ARG DATASTORE_VERSION="8.4"

doc/source/conf.py

@@ -38,8 +38,7 @@ extensions = ['sphinx.ext.todo',
 # openstackdocstheme options
 openstackdocs_repo_name = 'openstack/trove'
 openstackdocs_bug_project = 'trove'
-openstack_auto_name = False
-openstackdocs_bug_tag = ''
+openstackdocs_bug_tag = 'docs'
 html_theme = 'openstackdocs'
 
 # sphinxcontrib.apidoc options

doc/source/contributor/contributing.rst

@@ -14,7 +14,7 @@ Below will cover the more project specific information you need to get started
 with Trove.
 
 Communication
-~~~~~~~~~~~~~~
+~~~~~~~~~~~~~
 .. This would be a good place to put the channel you chat in as a project; when/
    where your meeting is, the tags you prepend to your ML threads, etc.
 
@@ -24,7 +24,7 @@ Communication
   reviewers and their timezones, the situation may change in the future.
 
 Contacting the Core Team
-~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~
 .. This section should list the core team, their irc nicks, emails, timezones etc. If
    all this info is maintained elsewhere (i.e. a wiki), you can link to that instead of
    enumerating everyone here.
@@ -46,15 +46,13 @@ New Feature Planning
 #. If a spec is need, a patch needs to be submitted to `trove-specs repo
    <https://opendev.org/openstack/trove-specs>`_ before the code being
    reviewed.
-#. Code implementation and review
+#. Code implementation and review.
 
 Task Tracking
-~~~~~~~~~~~~~~
-.. This section is about where you track tasks- launchpad? storyboard? is there more
-   than one launchpad project? what's the name of the project group in storyboard?
+~~~~~~~~~~~~~
 
-We track our tasks in `Storyboard
-<https://storyboard.openstack.org/#!/project/openstack/trove>`_
+We track our tasks in `Trove Launchpad
+<https://launchpad.net/trove>`_
 
 If you're looking for some smaller, easier work item to pick up and get started
 on, search for the 'low-hanging-fruit' tag.
@@ -65,7 +63,7 @@ Reporting a Bug
    your project.
 
 You found an issue and want to make sure we are aware of it? You can do so
-on `Storyboard <https://storyboard.openstack.org/#!/project/openstack/trove>`_.
+on `Trove Bugs Launchpad <https://bugs.launchpad.net/trove>`_.
 
 Getting Your Patch Merged
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -79,8 +77,8 @@ one +2 before ``Workflow +1``.
 Project Team Lead Duties
 ------------------------
 .. this section is where you can put PTL specific duties not already listed in
-   the common PTL guide (linked below)  or if you already have them written
+   the common PTL guide (linked below) or if you already have them written
    up elsewhere, you can link to that doc here.
 
 All common PTL duties are enumerated here in the `PTL guide
-<https://docs.openstack.org/project-team-guide/ptl.html>`_.
+<https://docs.openstack.org/project-team-guide/ptl.html>`_.

doc/source/contributor/release-notes.rst

@@ -91,8 +91,13 @@ Template
        Implements [some feature].
        [Can be described using multiple sentences if necessary.]
        [Limitations worth mentioning can be included as well.]
-       `Stroy [Story id] <https://storyboard.openstack.org/#!/story/[Story id]>`__
+       `Blueprint [blueprint id] <https://blueprints.launchpad.net/trove/+spec/[blueprint id]>`__
 
+.. note::
+
+  The blueprint can be mentioned even if the change implements it only
+  partially. This can be emphasised by preceding the ``Blueprint`` word by
+  ``Partial``. See the example below.
 
 Example
 +++++++
@@ -104,6 +109,13 @@ the scaffolded file:
 
    tox -e venv -- reno new --from-template releasenotes/templates/feature.yml blueprint-letsencrypt-https
 
+.. note::
+
+  Since we don't require blueprints for simple features, it is allowed to
+  make up a blueprint-id-friendly string (like in the example here) ad-hoc
+  for the proposed feature. Please then skip the ``blueprint-`` prefix to
+  avoid confusion.
+
 And then fill it out with the following content:
 
 .. code-block:: yaml
@@ -114,8 +126,14 @@ And then fill it out with the following content:
        Implements support for hassle-free integration with Let's Encrypt.
        The support is limited to operators in the underworld.
        For more details check the TLS docs of Trove.
-       `Stroy xxx <https://storyboard.openstack.org/#!/story/xxx>`__
+       `Partial Blueprint letsencrypt-https <https://blueprints.launchpad.net/trove/+spec/EXAMPLE>`__
 
+.. note::
+
+  The example above shows how to introduce a limitation. The limitation may be
+  lifted in the same release cycle and it is OK to mention it nonetheless.
+  Release notes can be edited later as long as they have not been shipped in
+  an existing release or release candidate.
 
 Fixes
 -----
@@ -132,7 +150,7 @@ Template
        Fixes [some bug].
        [Can be described using multiple sentences if necessary.]
        [Possibly also giving the previous behaviour description.]
-       `Stroy [Story id] <https://storyboard.openstack.org/#!/story/[Story id]>`__
+       `LP#[bug number] <https://launchpad.net/bugs/[bug number]>`__
 
 Example
 +++++++
@@ -150,5 +168,5 @@ And then fill it out with the following content:
    ---
    fixes:
      - |
-       Fixes ``create-datastore`` action doesn't work for the mysql datastore.
-       `LP#xxx <https://storyboard.openstack.org/#!/story/xxx>`__
+       Fixes ``deploy-containers`` action missing for the Masakari role.
+       `LP#1889611 <https://launchpad.net/bugs/1889611>`__

doc/source/index.rst

@@ -27,23 +27,20 @@ For an in-depth look at the project's design and structure, see the
    contributor/index
    reference/index
 
-
 * Source Code Repositories
 
   - `Trove`_
   - `Trove Client`_
 
 * `Trove API Documentation`_ on docs.openstack.org
-* `Trove storyboard`_ on storyboard.openstack.org
-
+* `Trove launchpad`_ on launchpad.net
 
 Search Trove Documentation
 ==========================
 
 * :ref:`search`
 
-
 .. _Trove: https://opendev.org/openstack/trove
 .. _Trove Client: https://opendev.org/openstack/python-troveclient
 .. _Trove API Documentation: https://docs.openstack.org/api-ref/database/
-.. _Trove storyboard: https://storyboard.openstack.org/#!/project/openstack/trove
+.. _Trove launchpad: https://launchpad.net/trove

releasenotes/source/conf.py

@@ -1,4 +1,3 @@
-# -*- coding: utf-8 -*-
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
@@ -44,9 +43,8 @@ extensions = [
 
 # openstackdocstheme options
 openstackdocs_repo_name = 'openstack/trove'
-openstack_auto_name = False
 openstackdocs_bug_project = 'trove'
-openstackdocs_bug_tag = ''
+openstackdocs_bug_tag = 'docs'
 html_theme = 'openstackdocs'
 
 # Add any paths that contain templates here, relative to this directory.

releasenotes/templates/feature.yml

@@ -4,4 +4,4 @@ features:
     Implements [some feature].
     [Can be described using multiple sentences if necessary.]
     [Limitations worth mentioning can be included as well.]
-    `Stroy [Story id] <https://storyboard.openstack.org/#!/story/[story id]>`__
+    `LP#[bug number] <https://bugs.launchpad.net/trove/[bug number]>`__

releasenotes/templates/fix.yml

@@ -4,4 +4,4 @@ fixes:
     Fixes [some bug].
     [Can be described using multiple sentences if necessary.]
     [Possibly also giving the previous behaviour description.]
-    `LP#[Story id] <https://storyboard.openstack.org/#!/story/[Story id]>`__
+    `LP#[bug number] <https://bugs.launchpad.net/trove/[bug number]>`__