Re: Do we release SC or not?

On Mon, Sep 6, 2010 at 9:35 AM, Thomas Thym <[email protected]> wrote:
>
>
> Am Monday 06 September 2010 17:29:25 schrieb Carl Symons:
> On Monday 06 September 2010 17:29:25 wrote Carl Symons:
>> On Mon, Sep 6, 2010 at 3:59 AM, Sebastian Kügler <[email protected]> wrote:
>> > On Friday, September 03, 2010 19:41:06 Aaron J. Seigo wrote:
>> >> On Thursday, September 2, 2010, Sebastian Kügler wrote:
>> >> > Everything I've heard until now (and that includes the whole "SC" idea)
>> >> > sounds just clumsy and doesn't feel practical. It's doable in paragraphs
>> >> > of text, but it's pretty much impractical for producing headlines.
>> >>
>> >> http://lists.kde.org/?l=kde-promo&m=128043108730686&w=2
>> >
>> > The idea sounds sound, but in practise to make it work, I find it sounding
>> > silly. Not so much for the x.y.0 releases, but for bugfix updates, it's almost
>> > Microsoft-ish. (Patchday, anyone?)
>> > --
>> > sebas
>> >
>>
>> Well, there are several ideas floating around this issue; "Release
>> Day" is only one of several. For me, the key is to communicate
>> something that connects properly with the audience (from a marketing
>> perspective). To use the bugfix update example, how about:
>>
>> ***KDE bugfix update***
>> Today KDE releases series 4.6.2 updates that include Applications and
>> Plasma Workspaces. While some new features are offered, the primary
>> emphasis for this Release Event is to continue improving quality and
>> to finetune existing features. These updates will improve the
>> performance of earlier KDE versions, so upgrading is recommended.
>>
>> Nothing Microsoft-ish about it. Facts, no vaporware, hype, cutesy terminology.
>>
>> Descriptive headline that speaks to how users are listening
>> Shared version number identifying the occasion--the Release Event
>> What is included and why
>>
>> Microsoft Patch Day has always occurred to me thusly...there are so
>> many things broken and breakable that we are committed to providing
>> patches monthly. Subtext - we won't get to them all, we hope to get to
>> most of the ones that are really broken, we will probably get to the
>> ones that cause us the most grief or hurt our revenues/relationships
>> with our best customers.
>>
>> This way of thinking is foreign to the way KDE operates.
>>
>> Carl
>
> From my (business) POV I personaly woud avoid pointing to bugs and other weaknesses in a release public spreaded announcement. I would prefer to mention it as "quality improvements" or " performance optimation / update" or something like that.
> (btw see the Snowleopard marketing.)
>
> Just for further brainstrorming: Carl, you mentioned "KDE releases series 4.6.2". So the "product" would be "KDE Series 4.6". Intresting. I read about the "KDE Suite 4.5" after our 4.5 release day. Were these two termes discussed yet?
>
> Cheers,
> Thomas
>

+1 on "quality improvements" and "performance optimization". The point
is - what is this release about *from the user/customer POV*? *Why
should users care?* Snow Leopard example is appropriate "...a simpler,
more powerful, and more refined version...", "...delivers a wide range
of enhancements, next-generation technologies...".

WRT "series 4.6.2", I just made that up based on some things others
have written. It's an imaginary example, not a product name
suggestion.

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