Congrats on a fantastic release of Plasma 5.12 everybody! People are
really gonna love it.
The release process was a bit rockier than expected, and I thought I
might do a post-mortem to see how we can make the next one smoother:
Problem: Initial request for release notes was not seen by many
===============================================================
Solutions:
- Send email to kde-pr...@kde.org and kde-de...@kde.org as well
- Use a Phabricator task instead of email to track overall work
- Make a subtask to track gathering release notes from developers
- Delegate a specific person (Ivanna?) to be responsible for turning the
release notes into final marketing copy
Problem: Unclear roles; nobody knew who owned the beta announcement
===================================================================
Solutions:
- Make roles and responsibilities clear to all; assign specific people
to specific tasks
- Make the KDE Promo crew the guardians of everything public-facing
Problem: Unclear access to the kde.org website
==============================================
(At once point, changes were requested and planned, but the one person
that everybody knew had access was on vacation)
Solutions:
- Define who should have access ahead of time
- Get those people access to the website ahead of time
Problem: Promo video produced at the last minute, gating final release
======================================================================
Solutions:
- Supply whomever is making the video with a pre-release copy of Plasma
5.12 at least a few days in advance so that the video can be completed
sooner
Thoughts?
Nate
