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

List:       koffice
Subject:    Re: Fwd: RE: koffice translations!!!
From:       Waldo Bastian <bastian () kde ! org>
Date:       2000-09-29 20:41:38
[Download RAW message or body]

On Thu, 28 Sep 2000, Byron C. Servies wrote:
> On 9/28/00 at 2:08 PM, me@caldera.de (Matthias Elter) wrote:
> > (...)
> >
> > > However, this is an open source project. And if you think that
> > > I ship an application from which I know that it is buggy in
> > > the math engine just because someone from caldera set a time
> > > schedule then you are wrong. I am sorry for the extra load
> > > on the translators. But I had no time before to make these fixes
> > > before and nobody else did them.
> >
> > I think we all agreed on the schedule. If you don't, write a reply when a
> > new schedule is posted, as it is always open for discussions. If you
> > however think that the schedule is made to fit Caldera's release plans,
> > feel free to take over the release dude job.
>
> Really?  I saw a grand total of 1 email related to schedule on the koffice
> lists, a reply from Waldo, and it indicated that there was a desire to move
> away from monolithic release schedule and a desire to avoid branching the
> tree.  I'd check the archives to see whether I'm mistaken, but they have
> never worked for me (pipermail always gives a link not found error).

My mail was a response to a mail from Matthias send to this list and others.

> Still, knowingly forcing a ship date on a major component that the author
> tells you is not ready is just stupid.  Imagine the result, Matthias, if
> you do your 'release dude job' to your schedule and ship a kspread that
> can't do math?  Were I the author, I'd forward all the flames to said
> release dude to handle.

If you are the author of an application and know your application is not 
ready in time you are supposed to say something about it. Nobody can track 
the progress of _ALL_ KDE applications. Matthias is in charge of the release. 
If your application is not ready in time you should inform Matthias about 
that so that the two of you can make an informed decision about what to do. 
(E.g. shipping as is, shipping in a later release, delaying the release). 

We can't just sit here and wait till all applications are finished because 
that point will never come. When your application is ready, mine isn't and 
vice versa... with 100 applications this is a bit of a problem.

That's also the main reason why these big monolithic releases are such a pain 
in the ass, we really shouldn't do that any more.

Cheers,
Waldo
-- 
KDE/Linux, you make the choice.

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