[kde-promo] Coordination of releases
sebas at kde.org
Thu Apr 13 13:47:28 BST 2006
On Thursday 13 April 2006 14:28, Stephan Kulow wrote:
> Am Donnerstag, 13. April 2006 14:02 schrieb Sebastian Kügler:
> > First, I'm glad that *someone* from the TWG finally replied on this
> > topic, and the more clear you are, the better.
> My vacation was nice though ;)
Glad to hear it. It's my turn next week then. :-)
> > Problem at hand: The last release was as uncoordinated as it could ever
> > be. Symptoms include: no message to kde-announce for days after the news
> > was on the dot. No translated press releases available. No single message
> > *for* the press. Instead of a bang, we made a fizzle.
> Yes, and it's all my fault as I kind of expected others to do the job. I
> can only work as much as I do, but I failed to communicate that I won't be
> able to do it. So I'm all for better defined responsibilities.
So let's try.
> > So the whole idea is: Less work for you, more time for us, better
> > releases in general because more people are involved and working together
> > in a coordinated fashion.
> > The problem is not forgetting stuff. The proposed timeline is there as an
> > orientation for what is helpful, at what point does it make sense to send
> > out reminders to who. It's there to answer questions such as "When should
> > we nag the TWG to give information about what?" - and to have clear
> > expectations for all involved parties.
> From my point of view, we're at a point where we need technical support for
> what we do - someone/something who's only responsibility is that certain
> milestones in the release are met. Originally that job should be the
> Release Coordinator, but as long as the Release Coordinator's timeline is
> already busy with version updates, preparing source packages, checking l10n
> compilation, reviewing branch commits and remerging for days, it's
> impossible for me to do that _and_ making sure the changelog is written and
> the announcement is translated in time.
Ok, we have a solution for parts of that already.
As to the ChangeLog: Carsten Niehaus kindly offered to do the changelog part.
Maybe he would be helped by a CCMAIL: changelog at kde.org for interesting /
important commits. (address doesn't exist yet, maybe a good idea to prevent
sucky release because Carsten's been hit by a bus?).
Translations of the release notes will be done by volunteers from local teams,
some of them already stepped up. [SKO] (More translation teams are welcome,
> After all I'm doing most of it in
> coffee breaks. In the past, a lot of that "nag work" was done by Stephan
> Binner and I kind of got used to get nagged :)
> So either someone declares responsible to nag me (or take over all of the
> above at once) or we need to define some technical process.
We're happy to help Beineri with the nagging part. If you have a tentative
release schedule, please send it over to kde-promo at kde.org (or if you wish to
keep it more confidential to kde-ev-marketing at kde.org) and we'll do our best
to keep track of it. Generally, the more information we get from you, the
easier we can nag, the less likely it is that we will have to, and the better
we can do our work (which involves getting it off your shoulders).
If you agree to collaborate on that proposal, we can try it for the upcoming
releases. I'll be happy to summarise what we agreed upon and put it up on a
webpage for everyone's reference.
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Which mindset is right? Mine, of course. People who disagree with me are by
definition crazy. (Until I change my mind, when they can suddenly become
upstanding citizens. I'm flexible, and not black-and-white.) - Linus Torvalds
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 483 bytes
Desc: not available
-------------- next part --------------
This message is from the kde-promo mailing list.
Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.
More information about the kde-core-devel