> -----Original Message-----
> From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 17, 2002 1:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [C2.1] Moving scratchpad goodies to main trunk
>
>
> On Friday 17 May 2002 13:09, Carsten Ziegeler wrote:
> > Nicola Ken Barozzi wrote:
> > > Scratchpad stuff is easy to change for the authors of the
> stuff, and for
> > > particular interested parties.
> > > IMHO, by putting them in HEAD, there could be 10-100 times more
> > > activity on
> > > it.
> > > In scratchpad you have to look for it, in HEAD you *have* to deal with
> > > it, wanting or not.
> > >
> > > What do others think?
> >
> > I totally agree and as we are currently in alpha state we can
> simply move
> > everything out of the scratchpad into main (if we want) and decide
> > before the first beta release which should better be put back into
> > scratchpad.
>
> ...I doubt putting it back will work. As soon as it's in main -
> someone will
> speak up NOT to move it back - whether it has the quality for beta or not.
> Or do I see this too problematic?
>
I personally think this is very easy: if it has not the quality for beta,
it can't be in the beta release. So there are two solutions:
a) some fixes that asap or
b) it's moved into scratchpad

For release often release early only b) is acceptable. Everyone should
understand this. It is not good to move a release date to infinity
because of "this is good new feature, it *must* be in the release,
but it's not working yet, just give me two more weeks". We did this
in the past with 2.0 which was acceptable for 2.0, but we shouldn't
do this mistake again. So release often, release early, but only
release beta quality is the slogan (for me)

> How do we separate stable and instable when we are about to make
> a release?
> I guess a release shouldn't wait for all the stuff that is currently in
> scratchpad to become stable... But that's how it is when
> everything goes into
> main... Isn't it?
See above.
We separate it at least by works or works not.

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to