[kde-community] Proposal Tre: More formal release and announcement processes

[Aleix Pol]

On Fri, Apr 25, 2014 at 9:12 PM, Jos Poortvliet <jospoortvliet at gmail.com>wrote:

> On Thursday 24 April 2014 08:11:26 Matthew Dawson wrote:
> > The whole proposal sounds good to me.  Just one minor point:
> >
> > On April 22, 2014 11:37:33 AM Mario Fux wrote:
> > > - Fill in the form on <siteB> with a list of links to blog posts about
> > > this
> > > release, a link to fixed bugs, 5 to 10 lines of text about what's new
> and
> > > important and a list of screenshots or pictures
> >
> > I'd recommend pre-filling out the list of bugs based upon information
> from
> > Bugzilla.  Since developers are already closing bugs using the BUG:
> keyword
> > on commits, this removes extra work from preparing the release
> > announcement. Release managers would of course be able to add/remove any
> > bugs not properly marked in Bugzilla.
>
> In general, I think what needs to happen is more automation. It might not
> have
> to be "fill in this form and the dot story, kde.org announcement and
> twitter
> messages are automatically written" but it would be a good pie in the sky
> ;-)
>

Isn't it part of KDE Promo to provide communcation from people to people?
Automating everything also renders the promo itself useless. Note that
everything promo says is available in tons of different automated formats
at the same time.

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20140426/692461f6/attachment.htm>