Re: Do we release SC or not?

On Tuesday 07 September 2010 03:07:58 Aaron J. Seigo wrote:
> On Sunday, September 5, 2010, Sebastian Kügler wrote:
> > I've thought of going this route as well, but wasn't really happy with
> > the outcomes I could imagine. 4.5.0 as an example:
> > 
> > "KDE Marble Brings Routing To the Free Desktop",
> > "Plasma's Notification Area Revamped"
> 
> this is focusing too closely on the details, imho. these would make good
> subheadings or attached articles, but for the main headline it could
> perhaps be: "New KDE Releases Provides Improvements For Your Mobile Life"

The problem is, why would I as a writer for some tech website not shorten that 
to "KDE 4.6 improves your mobile life"?

I'm not picking on your latest suggestion in particular, but it's something we 
have to answer:
- provide something versionless that's snappier
- don't have a KDE (SC) 4.6, either by changing our release naming or by 
splitting the releases
- some other magic?

We've had some take up of SC, imho because writers will give us an extra two 
letters in their headline because they know/think that's what we want and are 
humouring us

> > "Updated KDE Products Improves Stabiltiy, Performance,
> > Internationalization"
> > 
> > and variations of that theme. Nothing particularly exciting (especially
> > since we do have those releases once monthly).
> 
> "KDE SC 4.5.1" isn't exciting either. if anything, it's less exciting. so
> i'm not too concerned about this. :)
> 
> we also have two slightly different topics going here: one is about bug fix
> updates which happen at regular intervals and which have little
> differentiating benefits, and the other is how to frame our semi-annual
> releases.

Yep, but this whole thread came up because we didn't think through both of 
those together - we minimised use of SC for the 4.5 release, then put it right 
back in the headline for 4.5.1. We can look at them as separate problems, but 
the solutions need to work together.

> the monthly improvement releases probably do need a slightly separate
> treatment. we could simply boilerplate it with "September 2010 KDE Update
> Releases" and then get specific about which releases are out. we could even
> aggregate other update releases that happen on other days that month
> (Amarok, Digikam, KOffice) to get us all a bit more notice / press and
> give them sense of greater rhythm across our various projects.

"KDE's September Updates boost desktop performance" or variations. Fine

> > The case for putting release numbers into announcement titles is that it
> > makes it easier for journalists to write something, namely the usual
> > story: "KDE x.y.z is out, this and that has been fixed, yadda yadda..."
> 
> that's the body, not the headline. our announcement can have the version #
> in the body as well. i don't think our goal should be to have journalists
> headlining our version #s when we could have them headlining our virtues.

Ok, I was just about to argue with this and went to look how Apple and MS do 
things for some ammunition ;-) Um.. yeah. Turns out they mostly do what you're 
saying and it seems to work. So for 4.6 it might be more like (lets assume for 
a moment that PMC makes it into SC 4.6):

KDE Brings Your TV to Life with Plasma Media Center

rather than:

KDE's Release Day Introduces new Media Center Interface

or

KDE (SC) 4.6 Brings Your TV to Life with Plasma Media Center (the 'bad' option 
here is actually longer than the better one)

Ok, I understand a bit more now, adding those to the doc.

Stu
 
_______________________________________________
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.