Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2001:
[Freeciv-Dev] Re: Managing Long-Term Changes
Home

[Freeciv-Dev] Re: Managing Long-Term Changes

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Daniel Sjölie <deepone@xxxxxxxxxx>, "Per I. Mathisen" <Per.Inge.Mathisen@xxxxxxxxxxx>, freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Managing Long-Term Changes
From: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 21 Dec 2001 13:03:29 +0100
Reply-to: rf13@xxxxxxxxxxxxxxxxxxxxxx

On Fri, Dec 21, 2001 at 11:10:47AM +0100, Daniel Sjölie wrote:
> On 2001-12-21 10:42:52, Per I. Mathisen wrote:
> > On Fri, 21 Dec 2001, Reinier Post wrote:
> > > > How do ya'll manage long-term changes?  I am getting the impression
> > > > that a bunch of patches are sitting somewhere outside of the
> > > > repository and if you work on that section, you apply the patches.
> > >
> > > If only it were that organized ...
> > 
> > To be fair, we do have a bugtracking system that we send patches ready for
> > inclusion to. It is at "bugs@xxxxxxxxxxxxxxxxxxx". The maintainer
> > processes this queue of patches for inclusion, so nothing sent there gets
> > lost. But it is a slow process.
> > 
> > > Yes.  There seems to be a consensus on the list to create an 'unstable'
> > > branch, but the discussion stopped before all the details were clear.
> > 
> > I believe it stopped short because nobody volunteered to maintain or
> > manage that branch. But I'm not sure we need a "manager" for such a
> > branch... why not just give the most frequent patchers write access and
> > sort out problems as they arise. Perhaps finding someone who can be
> > "release manager" when that starts becoming an issue. I think the biggest
> > danger isn't introducing bugs, but turning off developers, and that has
> > happened a lot the last year(s).
> 
> I don't think we need an official manager to try this out... 

> Let's just create an unstable repository, 

Go ahead. Set one up at SF or somewhere else. 

> give anyone who has got a patch into cvs and wants to have it write
> access and see what happens...

Maybe chaos maybe not. Maybe there will someone emerge who organizes
this, maybe not. I would like to see such an experiment happen.

> If it all goes down the drain I don't think anything was lost,
> right?

Only time.

> I'd like to be one of those with write access...

        Raimar
-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 checking for the vaidity of the Maxwell laws on this machine... ok
 checking if e=mc^2... ok
 checking if we can safely swap on /dev/fd0... yes
    -- kvirc 2.0.0's configure 


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