Complete.Org: Mailing Lists: Archives: freeciv-dev: April 2002:
[Freeciv-Dev] Re: It is feature freeze time
Home

[Freeciv-Dev] Re: It is feature freeze time

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: "Per I. Mathisen" <Per.Inge.Mathisen@xxxxxxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: It is feature freeze time
From: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 27 Apr 2002 09:35:33 +0200
Reply-to: rf13@xxxxxxxxxxxxxxxxxxxxxx

On Sat, Apr 27, 2002 at 01:34:55AM +0200, Per I. Mathisen wrote:
> On Fri, 26 Apr 2002, Ross W. Wetmore wrote:
> > The sensible thing for the release beta is to spin off a branch
> > at feature freeze, and only allow bugfixes on that branch. The
> > regular CVS mainline can continue as the development branch.
> >
> > This sort of process management would probably result in a lot
> > less apologizing and general irritation all round - especially
> > that resulting from perceptions of the arbitrary favouritism.
> >
> > This also means you can continue beta fixing as long as you need
> > to get the thing stable without pressure from developers or
> > losing those you have, so there are benefits on both sides.
> 
> On Fri, 26 Apr 2002, Jason Short wrote:
> > I'd like to again suggest the use of CVS branches to minimize the
> > downtime from a feature freeze.
> 
> This has been up before... Actually, I remember suggesting this myself
> earlier. But I'm not sure about this.

> I want people here to make an effort to debug what we have now so that we
> can ship it.

I also see this problem. We have to avoid splitting the developers
base.

Now that the sound is in I have thought about the time schedule. I
have drawn one IMHO important conclusion:

  After we released the current version we will set a time (say 3
  months) and than really freeze the tree at that day. Even when the
  most impressive feature is just to be applied. Even if is it "ready
  for inclusion". It will have to wait.

This may sound drastic but I don't see another way. From Jan till now
we have only got the sound in (two major goals were still open, one
has been dropped now). During this time the sound patch was changed in
a major way (the complete way how the information is transfered from
the server to the client was revised).

So I learned that the original way posted in Jan from me was wrong. I
would like to try the beta time with no extra branches and see what
will happen. It may also be helpful if Jason can describe (I wasn't
following the development very precisely at these days) what was the
problem at the previous beta time. Just too many bugs found? No fixes
were posted? Posted fix weren't committed?

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 "On the eigth day, God started debugging"


[Prev in Thread] Current Thread [Next in Thread]