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

[Jos Poortvliet]

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 ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20140425/4663a7c8/attachment.sig>