release process - suggestion

[Harald Sitter]

As KDE servers seem to take a while for sync, and as distros can put packages 
@ kde servers, it might be a good idea to have a delay between 
tagging/tarballing and actual public release.

So: do tagging on friday evening UTC, saturday morning UTC most servers should 
be in sync, packagers then can build binaries and people in #amarok can test 
the tarball.

So we can provide binaries at release, ensure that tarball builds everywhere  
and have still enough time to react on possible issues.

thoughts?

BTW, if KDE servers aren't in sync UTC morning tomorrow I will release 1.4.2 
on sf.net - kinda fed up with that version...... we also need a fixed release 
date, where either stable features go in, or they have to wait for next 
release

-- 
Harald Sitter      roKymotion team         harald.sitter at kdemail.net
amarok.kde.org     rokymotion.pwsp.net     apachelogger at kdetalk.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/amarok/attachments/20060822/2d4a8649/attachment.sig>