[openbeos] Re: Organizational question

Niels Reedijk <Niels.Reedijk@xxxxxxxxx> wrote:
> > I read a short introduction to arch as well, and I think it's way 
> > to
> > complicated to create a patch and to submit it. IMO let's rather 
> > wait
> > for a later version or branch of it before thinking to adopt it; 
> > it's a
> > bit too simple in what it does now.
> If really all you want to do is create a small patch for a bug that
> has been hitting you like a rock for a long time, then there's 
> nothing
> wrong with using the standard gnu patch utils. However, if you are
> developing a larger feature, you might need a bit more time to do so.

I happen to be one of those developers who would probably be slowed 
down considerably, so at least I don't want to have it for now :)

> In the meanwhile, arch allows you to keep up to date with the
> changesets in the 'mainline'. If it is ready, and tested, than you 
> can
> opt in for inclusion. Or consider a company that makes a 
> customization
> to tracker (a logo). With arch they can keep their own changes, and
> stay up to date with the changesets in the mainline as well, because
> arch uses intelligent merges.

If it's just a logo, the same is possible even with CVS. Also, the arch 
introduction seem to advertise the possibility of having only some 
developers working with arch for a start - dunno how that is supposed 
to work in combination with CVS, but maybe there are some tools as 
well.

> You see, software development is all about managing changesets. It is
> about managing how to make sure all the relevant changesets stay
> together. Arch is merely a tool to guide the changesets on their
> proper way, like a set of traffic rules. As soon as you get into that
> analogy, and into the concepts arch brings with it, you'll see that
> it's not complicated, nor an overkill.

Other versioning systems are able to maintain changesets much simpler 
than arch does; and I see no reason for having distributed repositories 
anyway. The branch feature is always your friend.

Bye,
   Axel.

Other related posts: