[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    Re: [kde-promo] KDE 4.0 release party
From:       "=?ISO-8859-1?Q?Franz_Keferb=F6ck?=" <franz.keferboeck () gmail ! com>
Date:       2007-08-23 17:14:13
Message-ID: 41891b250708231014h2b953cdcs1791d5623a1c4e51 () mail ! gmail ! com
[Download RAW message or body]

On 23/08/07, Eric Krüse <bildvontux@yahoo.de> wrote:
> We are releasing in October, why a January party and why in the week?

The 4.0.0 will be released October, no change to that. This will be
the .0.0 release, which - which could be delayed due to showstopper
bugs, will not have all important 3rd party software ported by then
(neither Amarok, nor KOffice will be released then), ... .
The release party in turn needs a fixed date: invited people need to
book flights, the Hotel has to be booked as well, Google will have to
prepare - and Wade, Troy, me and some others are planning for it to be
really cool (think: you can't shift aKademy for a showstopper bug...).
So we _need_ the date absolutely fixed, so we decided to release with
4.0.1, which will have some .0.0 defects ironed out, ...

So much for "why in january"...

Greets
Franz

> 
> "Aaron J. Seigo" <aseigo@kde.org> schrieb:
> On Wednesday 22 August 2007, Troy Unrau wrote:
> > I am not happy working in secrecy forever as that is not what KDE is
> > about. We are far enough along that those that would be poisonous to
> > the event planning could no longer exert their control on this event,
> > and our team is pretty much set as it exists right now.
> 
> agreed. i'm just fine with talking about the release event in general. we've
> been doing that for a few months now, actually.
> 
> but specifically what i'm concerned about is the level of certain details
> covered in that blog entry. for instance, we now have 5 months where some
> other project could beat us to the punch of hosting their release event at
> google. it's not the end of the world, but it adds some risk that our event
> won't be as media interesting (which is in part derived from uniqueness; if
> everyone's doing it, it's boring. if we're the first to do something, it's
> very interesting)
> 
> i'd also prefer for us stage the release of the various details over time
> versus all at once in a blog entry; this probably just means we have more
> riding on the people we get to attend as presenters now as that's one of the
> remaining bits we can still talk about and it be news.
> 
> these are things we can do Better(tm) with through coordination. it's not a
> life ending issue.
> 
> > By the way, releasing little bits of information at a time is how you
> > build hype.
> 
> i agree.
> 
> > Cheers folks, and once again it seems I'm stepping on people's toes.
> 
> that's part of working in a group, yes. fortunately we all have pretty tough
> toes and tend to tell each other when someone is on them.
> 
> > It's a good time to take a break :)
> 
> enjoy your vacation =)
> 
> 
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
> 
> KDE core developer sponsored by Trolltech
> 
> _______________________________________________
> 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.
> 
> 
> ________________________________
> Yahoo! Clever: Stellen Sie Fragen und finden Sie Antworten. Teilen Sie Ihr
> Wissen.
> 
> 
> 
> _______________________________________________
> 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.
> 


-- 
Kepler University Linz
KDE Marketing - http://www.kde.org
 
_______________________________________________
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.


[prev in list] [next in list] [prev in thread] [next in thread]