I would like to nominate myself as vice-chair of the
Technical Committee for Zed cycle.
This is my first time ever in TC and I know I have to
learn a lot but I think that being vice-chair and
helping our chair in day-to-day duties will speed up
my ramping up process and I'm positive that I can be
a good vice-chair.
Thanks for considering my nomination.
Change-Id: I171ca2de884b183adf856cbc60d1e9a5591c0183
sushy-oem-idrac is iDRAC specific OEM extension of vendor-independent
sushy library and both use Redfish to communicate with BMCs in Ironic.
It has been proposed to be owned by Hardware SIG at openstack-discuss
mailing list [1].
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027418.html
Change-Id: I0f011af28c8aee9a14d666ff7fc1715d7edd592d
governance tooling use gerrit account query to check the
vote count (https://review.opendev.org/accounts/<email>)
and it seems that is case sensitive. It cannot find the
account for Arne as email listed in members file is not
in upper letters what gerrit has.
Change-Id: Ie063a9e239ac482e9dc3e4ecf2f60c13b2a700b1
In the TC guide document there was still link to the
user-committee-repos.yaml file which was removed by patch [1].
This patch removes that link from the TC guide document.
[1] https://review.opendev.org/c/openstack/governance/+/797788
Change-Id: I3e3d38de3b4ce507a6b8a03974c0b2cbae4b27dd
We don't use openstack-dev mailing list since some time. This patch
changes it to point to openstack-discuss which is currently used and
active mailing list.
Change-Id: Ic559a67ec661d896d9b266a916cfc10a318d23ce
I would like to nominate myself as chair of the
Technical Committee for Zed cycle.
I served as TC Chair in xena and Yoga cycle and trying my
best to be more active in TC and perform chair all duties
on time.
I would like to continue the chair role and improve the
TC interaction with rest of the community, engage TC in doing
more technical things, and help OpenStack community to achieve the
common goals.
Thanks for considering my nomination.
Change-Id: I0fbc55d06fad59f9fc7d46514324b9c836608461
It drop the centos8 stream and py3.6 testing. I did
not add the ubuntu 22.04 as it is not yet released and
will be releases in April but we need to preare the Zed
testing tempate before that. We will discuss it in PTG
and see if we need to update or not(but again based on
its release timming).
Change-Id: I8eaecfd51d5a34701758342dc8cc4e6c522de3bf
Since 2010, we went from 26 different OpenStack releases names
(from "A" - "Austin" to "Z" - "Zed"). It's now time to define an
unambiguous and sustainable release schema to easily identify
different OpenStack releases without taking into account the alphabet
iteration.
With this change the TC proposes to move the release identification
from only a release name (ex: "Axxxx") to "year"."release count within
the year" "release name" (ex: 2023.1 Axxxx). This will help to bring
more clarity for releases support and future feature deprecations.
The release name will continue to be used for marketing purposes and
community engagement. The same release name process and criteria will
continue to be used. When the end of the alphabet is reached we start
again from the first letter of the alphabet (after "Z", the next
name should start with "A" again).
The release number of each individual project is independent of the
release identification/name.
Change-Id: I595504a101138ee4a2afd358dc4af8f6617aa845
The VMT has moved all relevant information previously conveyed by
the vulnerability:managed governance tag into its own documentation,
so this can be safely removed.
Change-Id: I69c7f73403ddef74078715f72b3548f46b849581
Depends-On: https://review.opendev.org/830476
