[qa][release][tripleo] Abandoning openstack-tempest-skiplist?
hberaud at redhat.com
Wed Jan 20 09:07:54 UTC 2021
@Mario: Patch LGTM I think you can stop holding it, and I think we can
propose to delete the release file on openstack/release with a depends-on
@Ghanshyam: Thanks for the heads-up about Tripleo.
Le mar. 19 janv. 2021 à 19:44, Ghanshyam Mann <gmann at ghanshyammann.com> a
> ---- On Tue, 19 Jan 2021 10:34:20 -0600 Marios Andreou <marios at redhat.com>
> wrote ----
> > On Fri, Jan 15, 2021 at 4:56 PM Ghanshyam Mann <gmann at ghanshyammann.com>
> > ---- On Fri, 15 Jan 2021 03:07:12 -0600 Herve Beraud <
> hberaud at redhat.com> wrote ----
> > > Dear QA team,
> > > The release team noticed an inconsistency between the QA team's
> deliverables described in the governance’s reference and deliverables
> defined in the openstack/releases repo (c.f our related meeting topic ).
> > > Indeed, openstack-tempest-skiplist (added Mar 20, 2020) was never
> released yet, was not ready yet for ussuri and victoria. maybe we should
> abandon this instead of waiting?
> > > Notice that Wallaby's milestone 2 is next week so maybe it could be
> a good time to update this.
> > > Let us know your thoughts, we are waiting for your replies.
> > > Thanks for reading,
> > Thanks hberaud for brining it,
> > I did not know about this repo until it was discussed in yesterday's
> release meeting.
> > As per the governance project.yaml 'openstack-tempest-skiplist' is
> under the TripleO project, not QA  (tagging tripleo in sub).
> > This repo is to maintain the test skiplist so not sure if it needed
> release but marios or Chandan can decide.
> > 
> > -gmann
> > Thank you Herve and Ghanshyam (and thanks Chandan for pointing me to
> this thread!)
> > apologies for the late response but I initially missed this.
> > I just discussed a bit with Arx (adding him into cc) - he agrees this
> isn't something we will want or need to make releases for. It is used by CI
> tooling and not to do with TripleO deploying OpenStack.
> > The repo itself is branchless so if we *want* to make releases for it
> then we can consider adding a release file under deliverables/_independent
> in the releases repo.
> > However since we don't then I think we should just mark it so in
> governance? I posted that just now there
> https://review.opendev.org/c/openstack/governance/+/771488@Herve is that
> Thanks, marios for your response and updates. I also agree that this skip
> list repo does not need release as such.
> > regards, marios
> > > 
> > > --
> > > Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://
> > > -----BEGIN PGP SIGNATURE-----
> > >
> > > wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+
> > > Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+
> > > RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP
> > > F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G
> > > 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g
> > > glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw
> > > m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ
> > > hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0
> > > qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y
> > > F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3
> > > B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O
> > > v6rDpkeNksZ9fFSyoY2o
> > > =ECSj
> > > -----END PGP SIGNATURE-----
> > >
> > >
Senior Software Engineer at Red Hat
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss