[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-devel-list
Subject: Re: Proposal: Add release announcement post to Go/No-Go criteria
From: Jaroslav Reznik <jreznik () redhat ! com>
Date: 2018-09-26 14:08:30
Message-ID: CAMDqk57jbwVh1=bxY--Q+H_6R3dj4PoQQtkRmbf3wUjJA=D+hw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, Sep 26, 2018 at 12:38 AM Matthew Miller <mattdm@fedoraproject.org>
wrote:
> On Tue, Sep 25, 2018 at 04:35:09PM -0400, Ben Cotton wrote:
> > With today's Beta release, the release announcement post for Fedora
> > Magazine was not ready. As a result, the announcement went out a
> > little late and then only due to a drop-everything effort (thanks,
> > stickster!). We have a proposal to add a fourth criterion for the
> > Go/No-Go decision, beginning with F29 Final:
>
> Isn't this supposed to be the point of the release-readiness meeting that
> follows go/no-go?
>
Indeed, it is part of the readiness meeting but even that might not be
sufficient sometimes. This happened to me once that the Beta release
announcement wasn't really ready (and I had to write it then...) even I was
told on the readiness meeting it is ready :). And it's a knowledge that
somehow transferred from Program Manager to Program Manager to always
recheck the status but it gets lost over generations :))) (and you're doing
a great job Ben!). Go/No-Go meeting is really a not a good candidate but
maybe some changes to how the Readiness meeting is done might help. Instead
of status meeting we can change it more to the Readiness Check-list like
thing with predefined tasks that are neccessary for the release. Just one
note - afaik Readiness meeting does not block the release automatically if
something is not ready but I believe it's kind of common sense to block
when something like announcement is not ready (but you always have like 5
days between first possible GA date and Readiness meeting).
Thanks,
Jaroslav
>
> --
> Matthew Miller
> <mattdm@fedoraproject.org>
> Fedora Project Leader
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
--
Jaroslav Řezník <jreznik@redhat.com>
Engineering Program Manager
Office: +420 532 294 645
Mobile: +420 602 797 774
Red Hat, Inc. http://www.redhat.com/
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Wed, Sep 26, 2018 \
at 12:38 AM Matthew Miller <<a \
href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Sep 25, 2018 at \
04:35:09PM -0400, Ben Cotton wrote:<br> > With today's Beta release, \
the release announcement post for Fedora<br> > Magazine was not ready. \
As a result, the announcement went out a<br> > little late and then only \
due to a drop-everything effort (thanks,<br> > stickster!). We have a \
proposal to add a fourth criterion for the<br> > Go/No-Go decision, \
beginning with F29 Final:<br> <br>
Isn't this supposed to be the point of the release-readiness meeting \
that<br> follows go/no-go?<br></blockquote><div><br></div><div>Indeed, it \
is part of the readiness meeting but even that might not be sufficient \
sometimes. This happened to me once that the Beta release announcement \
wasn't really ready (and I had to write it then...) even I was told on \
the readiness meeting it is ready :). And it's a knowledge that somehow \
transferred from Program Manager to Program Manager to always recheck the \
status but it gets lost over generations :))) (and you're doing a great \
job Ben!). Go/No-Go meeting is really a not a good candidate but maybe some \
changes to how the Readiness meeting is done might help. Instead of status \
meeting we can change it more to the Readiness Check-list like thing with \
predefined tasks that are neccessary for the release. Just one note - afaik \
Readiness meeting does not block the release automatically if something is \
not ready but I believe it's kind of common sense to block when \
something like announcement is not ready (but you always have like 5 days \
between first possible GA date and Readiness \
meeting).</div><div><br></div><div>Thanks,</div><div>Jaroslav</div><div> \
</div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
-- <br>
Matthew Miller<br>
<<a href="mailto:mattdm@fedoraproject.org" \
target="_blank">mattdm@fedoraproject.org</a>><br> Fedora Project \
Leader<br> _______________________________________________<br>
devel mailing list -- <a href="mailto:devel@lists.fedoraproject.org" \
target="_blank">devel@lists.fedoraproject.org</a><br> To unsubscribe send \
an email to <a href="mailto:devel-leave@lists.fedoraproject.org" \
target="_blank">devel-leave@lists.fedoraproject.org</a><br> Fedora Code of \
Conduct: <a href="https://getfedora.org/code-of-conduct.html" \
rel="noreferrer" target="_blank">https://getfedora.org/code-of-conduct.html</a><br>
List Guidelines: <a \
href="https://fedoraproject.org/wiki/Mailing_list_guidelines" \
rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
List Archives: <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><div>Jaroslav Řezník \
<<a href="mailto:jreznik@redhat.com">jreznik@redhat.com</a>></div><div>Engineering \
Program Manager</div><div><br></div><div>Office: +420 532 294 \
645</div><div>Mobile: +420 602 797 774</div><div>Red Hat, Inc. \
<a href="http://www.redhat.com/">http://www.redhat.com/</a></div></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic