On Fri, Sep 28, 2018 at 10:59 PM Ben Cotton wrote:
> I want to address a few comments in particular:
>
> > Kevin Fenzi:
> > I'm prefer to add a new milestone of 'day before release' and put it
> > there.
>
> The current schedule starts the "create the release announcement" on
> the day of the
I want to address a few comments in particular:
> Kevin Fenzi:
> I'm prefer to add a new milestone of 'day before release' and put it
> there.
The current schedule starts the "create the release announcement" on
the day of the Go/No-Go meeting. I don't think that makes much sense:
the
On Tue, Sep 25, 2018 at 4:35 PM 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
On Wed, Sep 26, 2018 at 09:07:55AM -0400, Ben Cotton wrote:
> I'd rather not put it in place, but it's the best option I see for
> addressing the symptoms. It would be better to fix the upstream
> problem: Marketing not getting enough input on the talking points. I'm
> not sure what the solution
On Tue, Sep 25, 2018 at 04:29:51PM -0700, Adam Williamson wrote:
> The readiness meeting is only run *once* - if we slip at the first
> go/no-go, we don't run another readiness meeting after the second one.
> (I don't know why that is, though.)
Huh. That seems like maybe the problem. Readiness
On Wed, Sep 26, 2018 at 12:38 AM Matthew Miller
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
On Wed, 2018-09-26 at 16:54 +0200, Clement Verna wrote:
> On Wed, 26 Sep 2018 at 14:44, Brian (bex) Exelbierd
> wrote:
>
> >
> > On Tue, Sep 25, 2018 at 11:25 PM Kevin Fenzi wrote:
> >
> > > On 09/25/2018 01:35 PM, Ben Cotton wrote:
> > > > With today's Beta release, the release announcement
On Tue, Sep 25, 2018 at 06:33:28PM -0300, Eduard Lucena wrote:
> Basically, the issue on the announcement is that is tight to the Talking
> Points, and almost any team is helping us with that. The Marketing task is
> to collect the Talking Points, not to create them, because we aren't the
> people
On Tue, Sep 25, 2018 at 6:38 PM Matthew Miller wrote:
> Isn't this supposed to be the point of the release-readiness meeting that
> follows go/no-go?
>
Sort of. The Release Readiness meeting is more informative than
decision-making. And historically, we've only held it once. Eduard did
bring up
On Tue, 2018-09-25 at 18:37 -0400, Matthew Miller 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
On 09/26/2018 06:55 AM, Matthew Miller wrote:
> On Tue, Sep 25, 2018 at 02:24:16PM -0700, Kevin Fenzi wrote:
>> I'm prefer to add a new milestone of 'day before release' and put it
>> there. I think after the 'go' some folks who would be helpful in making
>> the announcement have more time to
On Wed, 26 Sep 2018 at 14:44, Brian (bex) Exelbierd
wrote:
>
>
> On Tue, Sep 25, 2018 at 11:25 PM Kevin Fenzi wrote:
>
>> On 09/25/2018 01:35 PM, Ben Cotton wrote:
>> > With today's Beta release, the release announcement post for Fedora
>> > Magazine was not ready. As a result, the announcement
On Tue, Sep 25, 2018 at 02:24:16PM -0700, Kevin Fenzi wrote:
> I'm prefer to add a new milestone of 'day before release' and put it
> there. I think after the 'go' some folks who would be helpful in making
> the announcement have more time to devote to it. Also, it would seem sad
> to me to be
On Tue, Sep 25, 2018 at 06:33:28PM -0300, Eduard Lucena wrote:
> Basically, the issue on the announcement is that is tight to the Talking
> Points, and almost any team is helping us with that. The Marketing task is
Almost *no* team, right? I've seen those posts and crickets in return.
--
On Tue, Sep 25, 2018 at 11:25 PM Kevin Fenzi wrote:
> On 09/25/2018 01:35 PM, 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
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
On Tue, Sep 25, 2018 at 4:44 PM Ben Cotton wrote:
> We have a proposal to add a fourth criterion for the
> Go/No-Go decision, beginning with F29 Final:
>
> 4. The release announcement post for Fedora Magazine is substantially
> complete
>
I'm torn on this one... I think the release announcement
In fact, and I'm going to take the fault on this, mattdm beta release
announcement in the RedHat portal[1] is so awesome, that makes look the one
on the Fedora Magazine like a robotic template. Because change set doesn't
provide context on why X or Y feature is good or awesome.
[1]
Basically, the issue on the announcement is that is tight to the Talking
Points, and almost any team is helping us with that. The Marketing task is
to collect the Talking Points, not to create them, because we aren't the
people that work on the new features and the stuff that make the release
On 09/25/2018 01:35 PM, 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
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
21 matches
Mail list logo
