RFC: Release Management Going Forward

[Dirk Mueller]

On Wednesday 22 June 2011, Albert Astals Cid wrote:

> > Personally, I don't see how we can continue releasing both monolithic and
> > split tarballs over a longer time, mostly due to work load reasons,
> > unless I find a way to script this together (which I doubt..).
> 
> What's stopping us from doing a script that does the release by just
> invoking one command?

Nothing, really. it already exists: /trunk/kde-common/release. the problem is 
more that the long list of configurations you need to adopt for every release 
(version numbers, branch names, module lists, various l10n fixups) are 
constantly changing. 

The git conversion made this completely painful. I hope this is settling down 
in the future again. 

Thanks,
Dirk