#265 Fedora release announcement in the future.
Closed 2 years ago Opened 3 years ago by mailga.

Along with the latest releases we used to publish the announce both in the wiki and in the magazine.
Obviously this meant a double engagement for the people working on it (and sometimes it wasn't synchronized).

Now we decided to edit only gthe magazine-side of the announce and in addition it could happen that edition and spins don't have the same availability day.

The questions are:

1) is every release announce (for each edition) still in charge on the Marketing Team?
2) if yes, how it can be handled?
3) if not, who's in charge to edit a new pitch in the magazine for each announce?
4) In this case, do we keep the opportunity of editing the pitch?

At the moment I'm not able to edit the pitch of the F27 release announce.

Gabri


Metadata Update from @mailga:
- Issue assigned to mailga

3 years ago

Metadata Update from @mailga:
- Issue tagged with: meeting, release announcement

3 years ago

@mailga For the last few releases (to my memory), the announcement is usually written by @mattdm with support from @bex and the Marketing team. If @mattdm also thinks it makes sense, I might propose the release announcement be a formal responsibility of the FPL, and they are encouraged to take advantage of the FCAIC and Marketing team to support them in that effort.

This way, the FPL engages with Marketing to feedback and eventually ports the announcement out to the Magazine. The FCAIC and Marketing can help provide feedback and the FPL would take initiative for the "doing" of this task.

Thoughts?

We need to split this in 2 major parts:

  • The Beta Release Announcement: It's fully up to the Marketing Team, revised by @mattdm and published both Magazine and Wiki.

  • The Final Release Announcement: For F26, as @jflory said, it was in charge of @mattdm. Also this release goes to the Magazine, but for all the media (news blogs, ML and others) it's handled by the announcements ML, but for F26 the announce was linking the Magazine, so we can take for sure that Magazine is were the Official Announcement is done.

So, to answer the questions:

  1. The Beta Release is in charge of the Marketing team, and I propose to still doing it this way. To the Final Release, I'm +1 with @jflory7's proposal of making it officially a task of the FPL.
  2. It's yes to the Beta: For the Beta Release, we create a text based in both the TP's and the change set. This should past through a team revision and a final FPL/Council revision.
  3. It's yes to the Final Release: For the Final release, it will be up to the FPL, and we can support it in any way it consider necessary.
  4. Again, for the Beta its up to us and for the Final Release is up to the FPL, but if will be nice if we can work synced for both announcements.

Hi @mailga ,

What do you think about the two previous answers??

The Beta Release is in charge of the Marketing team, and I propose to still doing it this way. To the Final Release, I'm +1 with @jflory7's proposal of making it officially a task of the FPL.

I'm +1 too.

Closing as completed,

the process will be:

The Beta Release Announcement: It's fully up to the Marketing Team, revised by @mattdm and published both Magazine and Wiki.

The Final Release Announcement: For F26, as @jflory said, it was in charge of @mattdm. Also this release goes to the Magazine, but for all the media (news blogs, ML and others) it's handled by the announcements ML, but for F26 the announce was linking the Magazine, so we can take for sure that Magazine is were the Official Announcement is done.

Metadata Update from @bt0dotninja:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata