Re: (xslide) indentation changes

[xslide S. <xsl...@me...>]

At 9 Oct 2003 22:57 -0400, Glen Peterson wrote:
 > I would be honored to recieve CVS access.
 > 
 > Two things about your other points:
 > 
 > 1.)  I wrote "merge", but I really meant "check-in".  I merged all my

Understood.

 > 2.)  The word "branch" always makes me nervous, because it's so easy to
...
 > I have a feeling that I am not understanding exactly what you meant. 

Considering that I hadn't thought it through in great detail, that's
not too surprising.

 > Are you saying you don't want me posting unfinished ideas as patches and

No, I'm not telling you not to post patches, I'm trying to make it
easier for everybody: you, me, and anybody who wants to pick up your
patches.

I mentioned branches because it seemed to me that you were capable of
developing and implementing ideas faster than they could be integrated
into xslide.

 > you would rather have me make temporary branches to the code base to
 > test these ideas out?  Then delete or merge each branch as we decide on
 > them as a group?  I haven't worked that way before, but it might be a
 > good idea.  I don't know.  Sure, I'll try it.
 > 
 > A lot of projects on the web have an installable "latest stable" build
 > and a "development" build with future features. GNU Emacs, XEmacs,
 > Linux, and many others follow this model.  Maybe that would meet similar
 > needs?

There's multiple development models to choose from in the Open Source
world: Gentoo Linux, for example, maintains multiple kernel
distributions.

The stable/development model could work, but what about 'unstable'
development that takes longer than one release cycle?  I haven't
worked out the model for doing that with xslide as I've contemplated
adding Semantic support/parsing to xslide, so I'm open to suggestions.

xslide is currently at version 0.2.2 and heading for 0.2.3.  Maybe
there should be a stable branch and a development branch from which
the more stable parts are added to the stable branch (and brought to
real stability before making a stable release), or maybe the
development branch is periodically declared 'stable' (and then made
stable), or maybe there should be stable and development branches and
possibly multiple pie-in-the-sky branches for developing ideas such as
Semantic support.

Regards,


Tony Graham.