The question is "how do we balance getting the
release in a predictable manner versus letting spins ship when
they're ready"(bcotton,
16:22:11)
cloud ppc64le didn't ship because of an
intermittent failure on the one compose that happened to end up
being the RC(bcotton,
16:23:12)
fzatlouk suggests someone from Spin SIG signs
up for releng issues on Pagure so that they get an email with failed
deliverables with each build(bcotton,
16:29:52)
AGREED: It would be
nice to give Spins the ability to release after the main release if
they need to(bcotton,
16:34:58)
mattdm suggests giving each spin owner a "go"
button that they have to push in order for the spin to be
published(bcotton,
16:35:29)
ACTION: bcotton to
discuss mattdm's suggestion with releng(bcotton,
16:36:43)
SELinux denials the first few days after install(bcotton, 16:38:12)
No SELinux notifications were not seeing during
the last phase of testing(bcotton,
16:41:40)
The SELinux troubleshooting applet is no longer
on the default Workstation install(bcotton,
16:41:58)
ACTION: jlandato
propose changes to the release criteria to reflect the fact that the
SELinux troubleshooting applet is no longer in the default
Workstation install. The criterion shoudl be dropped or modified to
reflect reality(bcotton,
16:46:10)
fzatlouk to propose adding multilib upgrade to release criteria
bcotton to discuss mattdm's suggestion with releng
jlandato propose changes to the release criteria to reflect the fact that the SELinux troubleshooting applet is no longer in the default Workstation install. The criterion shoudl be dropped or modified to reflect reality
Action items, by person
bcotton
bcotton to discuss mattdm's suggestion with releng
jlanda
jlandato propose changes to the release criteria to reflect the fact that the SELinux troubleshooting applet is no longer in the default Workstation install. The criterion shoudl be dropped or modified to reflect reality
mattdm
bcotton to discuss mattdm's suggestion with releng