Add stein release note links

Pick up release note landing pages that have been added since the last
time the script was run.

Change-Id: I326bb20a26eef4b5df3f395a159bb918e45d8b54
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

deliverables/stein/barbican.yaml

@@ -19,13 +19,15 @@ branches:
   - location: 8.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'Some enhancements were made to the vault back-end.  It is now possible to specify
-    a KV mountpoint and use AppRoles to manage authentication.'
-  - 'We now run a Barbican specific Octavia gate to verify the Octavia load balancing
-    scenario.'
-  - 'The PKCS#11 plugin was modified to allow the hmac_keywrap_mechanism to be configured.  With
-    this change, Barbican can be deployed with Ultimaco HSMs.'
-  - 'It is now possible to deploy Barbican with the pkcs#11 backend using either a
-    Thales or an ATOS HSM via TripleO.'
-  - 'Fixes were made to ensure that the barbican-manage commands for key rotation
-    worked for the PKCS#11 plugin.'
+  - Some enhancements were made to the vault back-end.  It is now possible
+    to specify a KV mountpoint and use AppRoles to manage authentication.
+  - We now run a Barbican specific Octavia gate to verify the Octavia
+    load balancing scenario.
+  - The PKCS#11 plugin was modified to allow the hmac_keywrap_mechanism
+    to be configured.  With this change, Barbican can be deployed with
+    Ultimaco HSMs.
+  - It is now possible to deploy Barbican with the pkcs#11 backend using
+    either a Thales or an ATOS HSM via TripleO.
+  - Fixes were made to ensure that the barbican-manage commands for
+    key rotation worked for the PKCS#11 plugin.
+release-notes: https://docs.openstack.org/releasenotes/barbican/stein.html

deliverables/stein/castellan.yaml

@@ -8,7 +8,7 @@ repository-settings:
 releases:
   - diff-start: 0.18.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 8f112b9afbbc949c80f57a4f33df4e68ae9ea620
         repo: openstack/castellan
     version: 0.20.1

deliverables/stein/ceilometermiddleware.yaml

@@ -16,3 +16,4 @@ releases:
 branches:
   - location: 1.4.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/ceilometermiddleware/stein.html

deliverables/stein/cinder.yaml

@@ -4,11 +4,13 @@ release-model: cycle-with-rc
 team: cinder
 type: service
 cycle-highlights:
-  - 'Added multiattach and deferred deletion support for the RBD driver.'
-  - 'Numerous bug fixes have been integrated to address stability and reliability.'
-  - 'User experience improvements around driver initialization, data retained during
-    volume transfers and the information returned by commands.'
-  - 'Continued improvements in the backup service.'
+  - Added multiattach and deferred deletion support for the RBD driver.
+  - Numerous bug fixes have been integrated to address stability and
+    reliability.
+  - User experience improvements around driver initialization, data
+    retained during volume transfers and the information returned by
+    commands.
+  - Continued improvements in the backup service.
 repository-settings:
   openstack/cinder: {}
 releases:

deliverables/stein/congress.yaml

@@ -24,14 +24,15 @@ branches:
   - location: 9.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'Important new NFV fault management capabilities through the addition of
-    multiple new features in Congress integration with Nova, Tacker, and
-    Monasca.'
-  - 'The new JGress framework unlocks whole new classes of policy use by making
-    the state of the cloud as given by JSON APIs available for policy
-    evaluation. By adopting a JSON query language for expressing policy
-    directly over JSON API data, JGress enables deployers to plug-in new data
-    sources without being limited by the availability of integration drivers.'
-  - 'As with every release, we continue to make Congress more robust and stable
-    than ever with bug fixes and internal improvements.'
+  - Important new NFV fault management capabilities through the addition
+    of multiple new features in Congress integration with Nova, Tacker,
+    and Monasca.
+  - The new JGress framework unlocks whole new classes of policy use
+    by making the state of the cloud as given by JSON APIs available
+    for policy evaluation. By adopting a JSON query language for expressing
+    policy directly over JSON API data, JGress enables deployers to
+    plug-in new data sources without being limited by the availability
+    of integration drivers.
+  - As with every release, we continue to make Congress more robust
+    and stable than ever with bug fixes and internal improvements.
 release-notes: https://docs.openstack.org/releasenotes/congress/stein.html

deliverables/stein/cyborg.yaml

@@ -23,7 +23,7 @@ releases:
         repo: openstack/cyborg
     version: 2.0.0
 cycle-highlights:
-  - 'Add FPGA programming support'
-  - 'Add GPU drivers'
-  - 'DB re-work to align with NOVA placement api strategy'
+  - Add FPGA programming support
+  - Add GPU drivers
+  - DB re-work to align with NOVA placement api strategy
 release-notes: https://docs.openstack.org/releasenotes/cyborg/stein.html

deliverables/stein/designate.yaml

@@ -8,10 +8,11 @@ type: service
 repository-settings:
   openstack/designate: {}
 cycle-highlights:
-  - 'Added ``CAA`` recordset type for CA authorization for managed DNS Zones'
-  - 'Added ``NAPTR`` recordset type for service chaining and SIP management'
-  - 'Validation of project IDs when updating quotas'
-  - 'Added ``designate-status upgrade check`` command to aid in upgrades.'
+  - Added ``CAA`` recordset type for CA authorization for managed DNS
+    Zones
+  - Added ``NAPTR`` recordset type for service chaining and SIP management
+  - Validation of project IDs when updating quotas
+  - Added ``designate-status upgrade check`` command to aid in upgrades.
 releases:
   - projects:
       - hash: 59d8cab9bbe37529346728778e6dae79a3a57a2a

deliverables/stein/heat-agents.yaml

@@ -14,3 +14,4 @@ branches:
     name: stable/stein
 repository-settings:
   openstack/heat-agents: {}
+release-notes: https://docs.openstack.org/releasenotes/heat-agents/stein.html

deliverables/stein/heat-dashboard.yaml

@@ -13,3 +13,4 @@ releases:
 branches:
   - location: 1.5.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/heat-dashboard/stein.html

deliverables/stein/heat.yaml

@@ -25,12 +25,12 @@ branches:
   - location: 12.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'Heat now supports orchestrating stacks in remote OpenStack clouds, using credentials
-    stored by the user in Barbican.'
-  - 'It is now easier to recover from accidentally trying to replace a resource with
-    a version that conflicts with the existing resource.'
-  - 'New resource types in Heat add support for Neutron Layer 2 Gateways, Blazar,
-    and Tap-as-a-Service.'
-  - 'Support Glance web download image resource type, which allow get the image from
-    URL without pre-load it out side of Glance.'
+  - Heat now supports orchestrating stacks in remote OpenStack clouds,
+    using credentials stored by the user in Barbican.
+  - It is now easier to recover from accidentally trying to replace
+    a resource with a version that conflicts with the existing resource.
+  - New resource types in Heat add support for Neutron Layer 2 Gateways,
+    Blazar, and Tap-as-a-Service.
+  - Support Glance web download image resource type, which allow get
+    the image from URL without pre-load it out side of Glance.
 release-notes: https://docs.openstack.org/releasenotes/heat/stein.html

deliverables/stein/horizon.yaml

@@ -35,8 +35,8 @@ branches:
   - location: 15.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'Cinder Generic Groups admin panels are now supported'
-  - 'Added option to mitigate breach attacks'
-  - 'Added an upgrade_check management command'
-  - 'Custom templates for clouds.yaml and openrc files support'
+  - Cinder Generic Groups admin panels are now supported
+  - Added option to mitigate breach attacks
+  - Added an upgrade_check management command
+  - Custom templates for clouds.yaml and openrc files support
 release-notes: https://docs.openstack.org/releasenotes/horizon/stein.html

deliverables/stein/ironic.yaml

@@ -26,15 +26,15 @@ branches:
   - location: 12.1.0
     name: stable/stein
 cycle-highlights:
-  - 'Adds additional interfaces for management of hardware including
+  - Adds additional interfaces for management of hardware including
     Redfish BIOS settings, explicit iPXE boot interface option, and
-    additional hardware support.'
-  - 'Increased capabilities and options for operators including deployment
+    additional hardware support.
+  - Increased capabilities and options for operators including deployment
     templates, improved parallel conductor workers and disk erasure
     processes, deployed node protection and descriptions, and use of
-    local HTTP(S) servers for serving images.'
-  - 'Improved options for standalone users to request allocations of
+    local HTTP(S) servers for serving images.
+  - Improved options for standalone users to request allocations of
     bare metal nodes and submit configuration data as opposed to pre-formed
     configuration drives. Additionally allows for ironic to be leveraged
-    using JSON-RPC as opposed to an AMQP message bus.'
+    using JSON-RPC as opposed to an AMQP message bus.
 release-notes: https://docs.openstack.org/releasenotes/ironic/stein.html

deliverables/stein/keystone.yaml

@@ -23,18 +23,20 @@ branches:
   - location: 15.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'This release introduced Multi-Factor Authentication Receipts, which facilitates
-    a much more natural sequential authentication flow when using MFA.'
-  - 'The limits API now supports domains in addition to projects, so quota for resources
-    can be allocated to top-level domains and distributed among children projects.'
-  - 'JSON Web Tokens are added as a new token format alongside fernet tokens, enabling
-    support for a internet-standard format. JSON Web Tokens are asymmetrically signed
-    and so synchronizing private keys across keystone servers is no longer required
-    with this token format.'
-  - 'Multiple keystone APIs now support system scope as a policy target, which reduces
-    the need for customized policies to prevent global access to users with an admin
-    role on any project.'
-  - 'Multiple keystone APIs now use default reader, member, and admin roles instead
-    of a catch-all role, which reduces the need for customized policies to create
-    read-only access for certain users.'
+  - This release introduced Multi-Factor Authentication Receipts, which
+    facilitates a much more natural sequential authentication flow when
+    using MFA.
+  - The limits API now supports domains in addition to projects, so
+    quota for resources can be allocated to top-level domains and distributed
+    among children projects.
+  - JSON Web Tokens are added as a new token format alongside fernet
+    tokens, enabling support for a internet-standard format. JSON Web
+    Tokens are asymmetrically signed and so synchronizing private keys
+    across keystone servers is no longer required with this token format.
+  - Multiple keystone APIs now support system scope as a policy target,
+    which reduces the need for customized policies to prevent global
+    access to users with an admin role on any project.
+  - Multiple keystone APIs now use default reader, member, and admin
+    roles instead of a catch-all role, which reduces the need for customized
+    policies to create read-only access for certain users.
 release-notes: https://docs.openstack.org/releasenotes/keystone/stein.html

deliverables/stein/keystoneauth.yaml

@@ -35,3 +35,4 @@ repository-settings:
 branches:
   - location: 3.13.1
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/keystoneauth/stein.html

deliverables/stein/keystonemiddleware.yaml

@@ -18,3 +18,4 @@ releases:
 branches:
   - location: 6.0.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/keystonemiddleware/stein.html

deliverables/stein/kolla.yaml

@@ -31,9 +31,10 @@ releases:
         repo: openstack/kolla
     version: 8.0.1
 cycle-highlights:
-  - 'Completed addition of images and playbooks for the OpenStack Monitoring service,
-    Monasca.'
-  - 'Added an image and playbooks for the OpenStack Placement service, which has been
-    extracted from Nova into a separate project.'
-  - 'Added support for performing full and incremental backups of the MariaDB database.'
+  - Completed addition of images and playbooks for the OpenStack Monitoring
+    service, Monasca.
+  - Added an image and playbooks for the OpenStack Placement service,
+    which has been extracted from Nova into a separate project.
+  - Added support for performing full and incremental backups of the
+    MariaDB database.
 release-notes: https://docs.openstack.org/releasenotes/kolla/stein.html

deliverables/stein/manila-ui.yaml

@@ -18,3 +18,4 @@ releases:
 branches:
   - location: 2.18.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/manila-ui/stein.html

deliverables/stein/networking-hyperv.yaml

@@ -18,3 +18,4 @@ releases:
 branches:
   - location: 7.1.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/networking-hyperv/stein.html

deliverables/stein/networking-odl.yaml

@@ -24,3 +24,4 @@ releases:
 branches:
   - location: 14.0.0.0rc1
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/networking-odl/stein.html

deliverables/stein/neutron.yaml

@@ -39,16 +39,18 @@ branches:
   - location: 14.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'Support for strict minimum bandwidth based scheduling. With this feature, Nova
-    instances can be scheduled to compute hosts that will honor the minimum bandwidth
-    requirements of the instance as defined by QoS policies of its ports.'
-  - 'Network Segment Range Management. This features enables cloud administrators
-    to manage network segment ranges dynamically via a new API extension, as opposed
-    to the previous approach of editing configuration files. This feature targets
-    StarlingX and edge use cases, where ease of of management is paramount.'
-  - 'Speed up Neutron port bulk creation. The targets are containers / k8s use cases,
-    where ports are created in groups.'
-  - '(FWaaS) FWaaS v1 has been removed. FWaaS v2 is available since Newton release
-    and it covers all features in FWaaS v1. A migartion script is provided to convert
-    existing FWaaS v1 objects into FWaaS v2 models.'
+  - Support for strict minimum bandwidth based scheduling. With this
+    feature, Nova instances can be scheduled to compute hosts that will
+    honor the minimum bandwidth requirements of the instance as defined
+    by QoS policies of its ports.
+  - Network Segment Range Management. This features enables cloud administrators
+    to manage network segment ranges dynamically via a new API extension,
+    as opposed to the previous approach of editing configuration files.
+    This feature targets StarlingX and edge use cases, where ease of
+    of management is paramount.
+  - Speed up Neutron port bulk creation. The targets are containers
+    / k8s use cases, where ports are created in groups.
+  - (FWaaS) FWaaS v1 has been removed. FWaaS v2 is available since Newton
+    release and it covers all features in FWaaS v1. A migartion script
+    is provided to convert existing FWaaS v1 objects into FWaaS v2 models.
 release-notes: https://docs.openstack.org/releasenotes/neutron/stein.html

deliverables/stein/nova.yaml

@@ -6,26 +6,30 @@ type: service
 repository-settings:
   openstack/nova: {}
 cycle-highlights:
-  - 'It is now possible to run Nova with version 1.0.0 of the recently extracted placement
-    service, hosted from its own repository. Note that install/upgrade of an extracted
-    placement service is not yet fully implemented in all deployment tools. Operators
-    should check with their particular deployment tool for support before proceeding.
+  - It is now possible to run Nova with version 1.0.0 of the recently
+    extracted placement service, hosted from its own repository. Note
+    that install/upgrade of an extracted placement service is not yet
+    fully implemented in all deployment tools. Operators should check
+    with their particular deployment tool for support before proceeding.
     See the placement `install <https://docs.openstack.org/placement/latest/install/index.html>`_
     and `upgrade <https://docs.openstack.org/placement/latest/upgrade/to-stein.html>`_
-    documentation for more details. In Stein, operators may choose to continue to
-    run with the integrated placement service from the Nova repository, but should
-    begin planning a migration to the extracted placement service by Train, as the
-    removal of the integrated placement code from Nova is planned for the Train release.'
-  - 'Users can now specify a volume type when creating servers.'
-  - 'The compute API is now tolerant of transient conditions in a deployment like
-    partial infrastructure failures, for example a cell not being reachable.'
-  - 'Users can now create servers with Neutron ports that have quality-of-service
-    minimum bandwidth rules.'
-  - 'Operators can now set overcommit allocation ratios using Nova configuration files
-    or the placement API.'
-  - 'Compute driver capabilities are now automatically exposed as traits in the placement
-    API so they can be used for scheduling via flavor extra specs and/or image properties.'
-  - 'Live migration is now supported for the VMware driver.'
+    documentation for more details. In Stein, operators may choose to
+    continue to run with the integrated placement service from the Nova
+    repository, but should begin planning a migration to the extracted
+    placement service by Train, as the removal of the integrated placement
+    code from Nova is planned for the Train release.
+  - Users can now specify a volume type when creating servers.
+  - The compute API is now tolerant of transient conditions in a deployment
+    like partial infrastructure failures, for example a cell not being
+    reachable.
+  - Users can now create servers with Neutron ports that have quality-of-service
+    minimum bandwidth rules.
+  - Operators can now set overcommit allocation ratios using Nova configuration
+    files or the placement API.
+  - Compute driver capabilities are now automatically exposed as traits
+    in the placement API so they can be used for scheduling via flavor
+    extra specs and/or image properties.
+  - Live migration is now supported for the VMware driver.
 releases:
   - projects:
       - hash: c993d4fe2ffaadea76d5ae76eedfddc3a4c71346

deliverables/stein/octavia.yaml

@@ -8,15 +8,15 @@ type: service
 repository-settings:
   openstack/octavia: {}
 cycle-highlights:
-  - 'Octavia now supports load balancer "flavors". This allows an operator
+  - Octavia now supports load balancer "flavors". This allows an operator
     to create custom load balancer "flavors" that users can select when
-    creating a load balancer.'
-  - 'You can now enable TLS client authentication when using TERMINATED_HTTPS
-    listeners.'
-  - 'Octavia now supports backend re-encryption of connections to member
-    servers.'
-  - 'Metadata tags can now be assigned to the elements of an Octavia
-    load balancer.'
+    creating a load balancer.
+  - You can now enable TLS client authentication when using TERMINATED_HTTPS
+    listeners.
+  - Octavia now supports backend re-encryption of connections to member
+    servers.
+  - Metadata tags can now be assigned to the elements of an Octavia
+    load balancer.
 releases:
   - projects:
       - hash: 68b9d06dae65c20b26aa63b78884f94b6642c542

deliverables/stein/openstack-ansible.yaml

@@ -54,3 +54,4 @@ cycle-highlights:
 branches:
   - location: 19.0.0.0rc1
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/openstack-ansible/stein.html

deliverables/stein/os-ken.yaml

@@ -26,3 +26,4 @@ releases:
 branches:
   - location: 0.3.1
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/os-ken/stein.html

deliverables/stein/os-net-config.yaml

@@ -34,3 +34,4 @@ releases:
 branches:
   - location: 10.4.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/os-net-config/stein.html

deliverables/stein/oslo.concurrency.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 3.27.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: d56295b8a91ab1b6fe1cc402e58404d86d1cd97c
         repo: openstack/oslo.concurrency
     version: 3.28.1

deliverables/stein/oslo.config.yaml

@@ -7,18 +7,20 @@ type: library
 repository-settings:
   openstack/oslo.config: {}
 cycle-highlights:
-  - 'Added a Castellan config driver that allows secrets to be moved from on-disk
-    config files to any Castellan-compatible keystore. This driver lives in the Castellan
-    project, so Castellan must be installed in order to use it.'
-  - 'Added a config driver to read values from environment variables, which allows
-    configuration of services in containers without needing to inject a file. This
-    driver is enabled by default in oslo.config.'
-  - 'Added a config validation tool, ``oslo-config-validator``. This uses the oslo-config-generator
-    data to find options in a config file that are not defined in the service.'
+  - Added a Castellan config driver that allows secrets to be moved
+    from on-disk config files to any Castellan-compatible keystore.
+    This driver lives in the Castellan project, so Castellan must be
+    installed in order to use it.
+  - Added a config driver to read values from environment variables,
+    which allows configuration of services in containers without needing
+    to inject a file. This driver is enabled by default in oslo.config.
+  - Added a config validation tool, ``oslo-config-validator``. This
+    uses the oslo-config-generator data to find options in a config
+    file that are not defined in the service.
 releases:
   - diff-start: 6.4.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 7072a7552dcb58a60d08c73c1d002fdf1c5a6202
         repo: openstack/oslo.config
     version: 6.5.1

deliverables/stein/oslo.db.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 4.40.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: e64c6bb6970b61b9f8aa704c5b2ac6e1f9c382d3
         repo: openstack/oslo.db
     version: 4.41.1

deliverables/stein/oslo.i18n.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 3.21.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: e7b3ff20019dcde3796665eea7d5a1867e568630
         repo: openstack/oslo.i18n
     version: 3.22.1

deliverables/stein/oslo.log.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 3.39.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: a93c6ef98c8aeddc5a4ae87083689225fbc728bb
         repo: openstack/oslo.log
     version: 3.40.1

deliverables/stein/oslo.policy.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 1.38.1
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: cef105744d80023eed5ec7392f31e073f38ea765
         repo: openstack/oslo.policy
     version: 1.39.1

deliverables/stein/oslo.privsep.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 1.29.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 9391cbf297d6baad20a3b67a973dd671499278d3
         repo: openstack/oslo.privsep
     version: 1.30.1

deliverables/stein/oslo.reports.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 1.28.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: dde49a40dc59a094f41feb061176aad3dd63a2a0
         repo: openstack/oslo.reports
     version: 1.29.1

deliverables/stein/oslo.serialization.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 2.27.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 0371c1d7f518406d5d8c271606620c1ba396b6c7
         repo: openstack/oslo.serialization
     version: 2.28.1

deliverables/stein/oslo.versionedobjects.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 1.33.3
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 50474adf278c79e74c2dc44733f5b6158ba5e7d8
         repo: openstack/oslo.versionedobjects
     version: 1.34.1

deliverables/stein/oslo.vmware.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 2.31.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 04f82ae934fda23612f78b2be9dfb24b06268c87
         repo: openstack/oslo.vmware
     version: 2.32.1

deliverables/stein/osprofiler.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 2.3.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: 2b4786b5cc819c5d321d97e3cf9e1d5f24ebdb97
         repo: openstack/osprofiler
     version: 2.4.1

deliverables/stein/paunch.yaml

@@ -38,3 +38,4 @@ releases:
 branches:
   - location: 4.4.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/paunch/stein.html

deliverables/stein/puppet-aodh.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-aodh
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-aodh: {}

deliverables/stein/puppet-barbican.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-barbican
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-barbican: {}

deliverables/stein/puppet-ceilometer.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-ceilometer
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-ceilometer: {}

deliverables/stein/puppet-cinder.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-cinder
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-cinder: {}

deliverables/stein/puppet-cloudkitty.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-cloudkitty
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-cloudkitty: {}

deliverables/stein/puppet-congress.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-congress
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-congress: {}

deliverables/stein/puppet-designate.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-designate
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-designate: {}

deliverables/stein/puppet-ec2api.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-ec2api
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-ec2api: {}

deliverables/stein/puppet-freezer.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-freezer
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-freezer: {}

deliverables/stein/puppet-glance.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-glance
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-glance: {}

deliverables/stein/puppet-glare.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-glare
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-glare: {}

deliverables/stein/puppet-gnocchi.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-gnocchi
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-gnocchi: {}

deliverables/stein/puppet-heat.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-heat
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-heat: {}

deliverables/stein/puppet-horizon.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-horizon
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-horizon: {}

deliverables/stein/puppet-ironic.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-ironic
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-ironic: {}

deliverables/stein/puppet-keystone.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-keystone
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-keystone: {}

deliverables/stein/puppet-magnum.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-magnum
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-magnum: {}

deliverables/stein/puppet-manila.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-manila
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-manila: {}

deliverables/stein/puppet-mistral.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-mistral
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-mistral: {}

deliverables/stein/puppet-monasca.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-monasca
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-monasca: {}

deliverables/stein/puppet-murano.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-murano
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-murano: {}

deliverables/stein/puppet-neutron.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-neutron
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-neutron: {}

deliverables/stein/puppet-nova.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-nova
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-nova: {}

deliverables/stein/puppet-octavia.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-octavia
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-octavia: {}

deliverables/stein/puppet-openstack_extras.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-openstack-extras
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-openstack_extras: {}

deliverables/stein/puppet-openstack_spec_helper.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-openstack-spec-helper
 release-model: untagged
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 stable-branch-type: tagless
 repository-settings:

deliverables/stein/puppet-openstacklib.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-openstacklib
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-openstacklib: {}

deliverables/stein/puppet-oslo.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-oslo
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-oslo: {}

deliverables/stein/puppet-ovn.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-ovn
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-ovn: {}

deliverables/stein/puppet-panko.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-panko
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-panko: {}

deliverables/stein/puppet-placement.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-placement
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-placement: {}

deliverables/stein/puppet-qdr.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-qdr
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-qdr: {}

deliverables/stein/puppet-rally.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-rally
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-rally: {}

deliverables/stein/puppet-sahara.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-sahara
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-sahara: {}

deliverables/stein/puppet-senlin.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-senlin
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-senlin: {}

deliverables/stein/puppet-swift.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-swift
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-swift: {}

deliverables/stein/puppet-tacker.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-tacker
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-tacker: {}

deliverables/stein/puppet-tempest.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-tempest
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-tempest: {}

deliverables/stein/puppet-tripleo.yaml

@@ -41,3 +41,4 @@ releases:
 branches:
   - location: 10.4.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/puppet-tripleo/stein.html

deliverables/stein/puppet-trove.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-trove
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-trove: {}

deliverables/stein/puppet-vitrage.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-vitrage
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-vitrage: {}

deliverables/stein/puppet-vswitch.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-vswitch
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-vswitch: {}

deliverables/stein/puppet-watcher.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-watcher
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-watcher: {}

deliverables/stein/puppet-zaqar.yaml

@@ -1,7 +1,7 @@
 ---
 launchpad: puppet-zaqar
 release-model: cycle-trailing
-team: 'Puppet OpenStack'
+team: Puppet OpenStack
 type: other
 repository-settings:
   openstack/puppet-zaqar: {}

deliverables/stein/python-designateclient.yaml

@@ -14,3 +14,4 @@ releases:
 branches:
   - location: 2.11.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/python-designateclient/stein.html

deliverables/stein/python-keystoneclient.yaml

@@ -18,3 +18,4 @@ releases:
 branches:
   - location: 3.19.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/python-keystoneclient/stein.html

deliverables/stein/python-tackerclient.yaml

@@ -14,3 +14,4 @@ repository-settings:
 branches:
   - location: 0.15.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/python-tackerclient/stein.html

deliverables/stein/python-tripleoclient.yaml

@@ -38,3 +38,4 @@ releases:
 branches:
   - location: 11.4.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/python-tripleoclient/stein.html

deliverables/stein/python-zaqarclient.yaml

@@ -14,3 +14,4 @@ releases:
 branches:
   - location: 1.11.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/python-zaqarclient/stein.html

deliverables/stein/sahara.yaml

@@ -24,7 +24,8 @@ branches:
   - location: 10.0.0.0rc1
     name: stable/stein
 cycle-highlights:
-  - 'Sahara plugins are removed from core code for easier maintenance and upgrades.'
-  - 'Release of APIv2 as stable.'
-  - 'Improvements on boot from volume feature.'
+  - Sahara plugins are removed from core code for easier maintenance
+    and upgrades.
+  - Release of APIv2 as stable.
+  - Improvements on boot from volume feature.
 release-notes: https://docs.openstack.org/releasenotes/sahara/stein.html

deliverables/stein/searchlight.yaml

@@ -28,10 +28,11 @@ type: service
 repository-settings:
   openstack/searchlight: {}
 cycle-highlights:
-  - 'Searchlight now works with Elasticsearch 5.x'
-  - 'We have released a new vision to make Searchlight a multi-cloud application'
-  - 'Functional test setup has been improved'
-  - 'Searchlight now can work and be tested with Python 3.7'
+  - Searchlight now works with Elasticsearch 5.x
+  - We have released a new vision to make Searchlight a multi-cloud
+    application
+  - Functional test setup has been improved
+  - Searchlight now can work and be tested with Python 3.7
 branches:
   - location: 6.0.0.0rc1
     name: stable/stein

deliverables/stein/senlin.yaml

@@ -20,14 +20,15 @@ releases:
         repo: openstack/senlin
     version: 7.0.0
 cycle-highlights:
-  - 'Improved performance so that Senlin operations execute multiple orders of magnitude
-    faster.'
-  - 'Health policy v1.1 now allows a user to specify multiple types of detection modes.'
-  - 'Senlin APIs now issues synchronous failures in case of cluster/node lock, cooldown
-    in effect or action conflict.'
-  - 'Operators can now remove completed actions using action-purge subcommand in senlin-manage
-    tool.  This is useful for long-running clusters that have accumulated a large
-    number of actions in the database.'
+  - Improved performance so that Senlin operations execute multiple
+    orders of magnitude faster.
+  - Health policy v1.1 now allows a user to specify multiple types of
+    detection modes.
+  - Senlin APIs now issues synchronous failures in case of cluster/node
+    lock, cooldown in effect or action conflict.
+  - Operators can now remove completed actions using action-purge subcommand
+    in senlin-manage tool.  This is useful for long-running clusters
+    that have accumulated a large number of actions in the database.
 branches:
   - location: 7.0.0.0rc1
     name: stable/stein

deliverables/stein/stevedore.yaml

@@ -18,3 +18,4 @@ releases:
 branches:
   - location: 1.30.1
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/stevedore/stein.html

deliverables/stein/storlets.yaml

@@ -26,7 +26,8 @@ releases:
 repository-settings:
   openstack/storlets: {}
 cycle-highlights:
-  - 'Support Python 3 runtime for user code'
+  - Support Python 3 runtime for user code
 branches:
   - location: 3.0.0.0rc1
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/storlets/stein.html

deliverables/stein/swift.yaml

@@ -21,12 +21,12 @@ releases:
       - repo: openstack/swift
         hash: 179fa7ccd4d6faeacc989715887b69f9422a17b2
 cycle-highlights:
-  - 'Numerous improvements to the S3 API compatibility layer.'
-  - 'Several fixes and improvements for the data-encryption middleware, including
-    allowing multiple keymaster middlewares. This allows migration from one key provider
-    to another.'
-  - 'Operators have more control over account and container server background daemon
-    I/O usage with the new ``databases_per_second`` config option.'
-  - 'Erasure-coded data may now be rebuilt to handoff nodes. This improves data durability
-    when disk failures go unremedied for extended periods.'
+  - Numerous improvements to the S3 API compatibility layer.
+  - Several fixes and improvements for the data-encryption middleware,
+    including allowing multiple keymaster middlewares. This allows migration
+    from one key provider to another.
+  - Operators have more control over account and container server background
+    daemon I/O usage with the new ``databases_per_second`` config option.
+  - Erasure-coded data may now be rebuilt to handoff nodes. This improves
+    data durability when disk failures go unremedied for extended periods.
 release-notes: https://docs.openstack.org/releasenotes/swift/stein.html

deliverables/stein/taskflow.yaml

@@ -9,7 +9,7 @@ repository-settings:
 releases:
   - diff-start: 3.2.0
     projects:
-      - comment: 'procedural tag to handle release job failure'
+      - comment: procedural tag to handle release job failure
         hash: f9349f4301d3892fe797498c65d1c0768abc35a3
         repo: openstack/taskflow
     version: 3.3.1

deliverables/stein/tooz.yaml

@@ -30,3 +30,4 @@ releases:
 branches:
   - location: 1.64.2
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/tooz/stein.html

deliverables/stein/tripleo-common.yaml

@@ -54,3 +54,4 @@ releases:
 branches:
   - location: 10.7.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/tripleo-common/stein.html

deliverables/stein/tripleo-heat-templates.yaml

@@ -50,3 +50,4 @@ cycle-highlights:
 branches:
   - location: 10.5.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/tripleo-heat-templates/stein.html

deliverables/stein/tripleo-image-elements.yaml

@@ -38,3 +38,4 @@ releases:
 branches:
   - location: 10.4.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/tripleo-image-elements/stein.html

deliverables/stein/tripleo-puppet-elements.yaml

@@ -34,3 +34,4 @@ releases:
 branches:
   - location: 10.3.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/tripleo-puppet-elements/stein.html

deliverables/stein/tripleo-ui.yaml

@@ -27,3 +27,4 @@ releases:
 branches:
   - location: 10.3.0
     name: stable/stein
+release-notes: https://docs.openstack.org/releasenotes/tripleo-ui/stein.html