Re: Do we release SC or not?

On Saturday, September 04, 2010 19:38:33 Aaron J. Seigo 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.

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"

And a couple of others. My problem was that it'd only concentrate on an 
individual part, and I didn't want to leave anybody out. Then you'd end up 
with:

"New KDE Products Improve Usability"

(Which is actually not bad, but very low on details.) This kind of thing would 
work if we came up with a real story for a release. The Social Desktop is one 
very nice release story (different aspects of one theme, sufficiently unique 
to KDE: It was picked up very well). The problem is that  there is often no 
such theme, especially not for x.y.z releases, or that the significant 
improvements (our key points in the announcements are spread over different 
areas ("KDevelop now with Integrated Debugger Visualization, KHangMan has 20 
New Levels, all in Pink"):

"Updated KDE Products Improves Stabiltiy, Performance, Internationalization" 

and variations of that theme. Nothing particularly exciting (especially since 
we do have those releases once monthly).

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..."

I think we're getting closer here, though. Thanks for bringing it up.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
 
_______________________________________________
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.