Deliverables following the cycle-with-intermediary model are expected
to release multiple times throughout the development cycle. Since
monasca-thresh only released once last cycle, and has not done a
release yet this cycle, this proposes changing the release model to
cycle-with-rc so the expectation is only that it will release an RC by
the end of the cycle prior to doing the final release.
This is just a suggestion for the team to consider. The important point
is past the milestone-2 point, downstream planning starts happening
for what will be included in the release. We just want to try to avoid
the situation where downstream expects something to be included, but we
need to unexpectedly drop it from the coordinated release late in the
cycle.
For the team, please respond to this patch in one of the following ways:
* -1 this patch and follow up with an intermediary release
* +1 this patch and we will switch over the release model
* -1 this patch, but acknowledge a release will be done prior to the
RC1 deadline.
Change-Id: I795b118e090953d51fe9865b67499d3ca21eb9ff
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Deliverables following the cycle-with-intermediary model are expected
to release multiple times throughout the development cycle. Since
magnum-ui only released once last cycle, and has not done a
release yet this cycle, this proposes changing the release model to
cycle-with-rc so the expectation is only that it will release an RC by
the end of the cycle prior to doing the final release.
This is just a suggestion for the team to consider. The important point
is past the milestone-2 point, downstream planning starts happening
for what will be included in the release. We just want to try to avoid
the situation where downstream expects something to be included, but we
need to unexpectedly drop it from the coordinated release late in the
cycle.
For the team, please respond to this patch in one of the following ways:
* -1 this patch and follow up with an intermediary release
* +1 this patch and we will switch over the release model
* -1 this patch, but acknowledge a release will be done prior to the
RC1 deadline.
Change-Id: I36ad5513dc8dc5fa5dcc3003d7b32b46e88cb6ac
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Deliverables following the cycle-with-intermediary model are expected
to release multiple times throughout the development cycle. Since
cloudkitty only released once last cycle, and has not done a
release yet this cycle, this proposes changing the release model to
cycle-with-rc so the expectation is only that it will release an RC by
the end of the cycle prior to doing the final release.
This is just a suggestion for the team to consider. The important point
is past the milestone-2 point, downstream planning starts happening
for what will be included in the release. We just want to try to avoid
the situation where downstream expects something to be included, but we
need to unexpectedly drop it from the coordinated release late in the
cycle.
For the team, please respond to this patch in one of the following ways:
* -1 this patch and follow up with an intermediary release
* +1 this patch and we will switch over the release model
* -1 this patch, but acknowledge a release will be done prior to the
RC1 deadline.
Change-Id: I218ebeb6a7659cc714c18720b35c8456c2f02bae
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This allows the projects with a cycle-with-intermediary release model
to be able to automatically generate the yaml file with the correct
new branch.
Change-Id: I003e5d3d39cbb8961822b3fd2a384bf3c9f66f5e
This is a 26 week schedule for the Wallaby release. Planned release date
is April 14, 2021. We don't have a date set for a first half 2021 event,
but it is expected to be some time shortly after this date.
Change-Id: I6ba030f678879d32f99680c68dcd4bff9cc00032
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Bump openstack-governance requirements to 0.7.0 to pick up latest
governance parsing code, as the current state of governance files
will break anything <0.7.0.
Change-Id: I6306fc7a99419b4f1e7b56855f38e5ccb84eca13
A number of bug fixes have been committed to
manila's stable/train branch, fixing:
bug #1879754 - neutron port lookup
bug #1703581 - lvm driver fails to extend cifs
bug #1850264 - async message on share extend error
bug #1882590 - netapp vserver scoped driver auth
bug #1841035 - dell emc unity cifs ace creation
bug #1885956 - share type api creates db record on failure
bug #1887695 - systemctl proxying
bug #1887643 - netapp active directory config
bug #1863021 - eventlet monkey patching issue
bug #1688620 - netapp retrying migration abort
bug #1880747 - netapp default ipspace deletion
bug #1887694 - lvm driver share extension
bug #1888915 - lvm driver share deletion
No user facing API has been altered in a regressive
manner, no db schema changes have been committed
and the new configuration option added comes with
an appropriate default, and has no upgrade impact.
Change-Id: I005919bc6d03ca1ca173347021d78f168e88a5f1
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>