Re: Do we release SC or not?

On Sat, Sep 4, 2010 at 10:38 AM, Aaron J. Seigo <[email protected]> wrote:
> On Friday, September 3, 2010, Scott Kitterman wrote:
>> On Friday, September 03, 2010 06:19:52 pm Bart Otten wrote:
>> > 2010/9/3 Scott Kitterman <[email protected]>:
>> > > On Friday, September 03, 2010 01:44:11 pm Aaron J. Seigo wrote:
>> > >> On Thursday, September 2, 2010, Sebastian Kügler wrote:
>> > >> > "KDE 4.5.1 Improves User Experience"
>> > >> >
>> > >> > The "4.5.1 is out" is just one part of our message, the more
>> > >> > important part is the "improves UX" bit. In the above examples,
>> > >> > there's just no room for
>> > >>
>> > >> is the release number important in the title?
>> > >
>> > > Yes.
>> > >
>> > > Scott K
>> >
>> > I gonna ask some people.....maybe it is, maybe it isn't. We are a
>> > bunch of nerds that live with svn4958345.45.1 names because we want to
>> > know if we are on the edge. Maybe regular people don't care....
>>
>> The release artifact needs a label.  It could be Bob, Fred, and Earl if we
>> preferred.  I think numbers work better, than names as a rule, but it needs
>> an identifying label.  Without a label we can't name what we're talking
>> about.
>
> i asked if it was needed in the title of the press release, not if it was
> needed at all. :)
>
> i agree that we need a label for all sorts of reasons ranging from packaging
> to bug report management to being able to compare who's got the most bleeding
> edge system for bragging rights ;) .. but we are assuming that we must have
> version numbers in our release announcement headlines in these conversations,
> and i'm not sure that we do.
>
> the headline can focus on the highlight benefit(s) of the release, the numbers
> and other details can appear in the body of the announcement. i've noticed
> that linux kernel releases are happening in batches these days and so stories
> about them often don't contain the 3 or 4 release numbers in the headline,
> just in the body.
>
> --
> Aaron J. Seigo

I like headline w/benefits or other news/so what-ness. The version
number is not really key to the news. For example, compare the impact
on the desired audience of "KDE releases 4.5 Development Platform" vs
"Latest KDE release includes 1,723 new features and 16,022 bug fixes".
In the universe of everyone-who-is-interested-in-KDE, the version
number has meaning for far fewer people than the progress represented
by the numbers.

The first part of the announcement amplifies features & benefits.
Details--including version number--are covered further along in the
body of the announcement.

The Linux kernel analogy is appropriate, at least for me. I have only
a faint idea of what version I'm running, probably 2.6.in the thirties
somewhere.

I announced the latest KDE release at the local LUG meeting last
Thursday. No one asked about the version number; they wanted to know
if I liked it and differences I noticed. Mostly I talked about how
smooth everything works and how easy & trouble-free the upgrade was. I
mentioned a problem with Intel graphics and Lanczos scaling--how it
messed up the graphics, how quickly it was solved on kde.bugs, passing
along the fix on some user forums. I suggested that anyone who's been
holding back ought to upgrade to the latest version for their
distribution. No mention, no questions about the version number.

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.