[crossfire] Crossfire Release Cycles/Methodology

[Alex Schultz]

Mark Wedel wrote:
> Per the recent discussion on code reorganization and what goes in what
> release, this document is an attempt to gather the points raised and make it
> into a formal document that can be included in the code or put on the wiki.
>
> <snipped the large list>
Those rules seem to make alot of sense to me. I can't think of any
disagreement I have with them.
> ------------------------------------------------------------------------------
> Open Issues:
>
> - Should we switch to SVN?  Switching repositories at same time as switching
>    what the head branch means would make the most sense.
>   
I agree that when switching what the head branch means makes the most
sense, however I'm not sure that to SVN would be a great type of move to
me. SVN from what I've seen does address some of CVS's weaknesses,
however I have heard that the way it handles branching for example is
ugly. Could someone with more experience with SVN comment on branching
in SVN? Also, if we are willing/able to move off of sf.net for version
control, it might be worth considering other version control options (I
personally think that if we don't use either SVN or CVS, we should see
if we can set up a read-only CVS or SVN mirror for people to download
off of who don't have the other type of version control software.)
> - Need some way to drive development - need some way to make sure items
>    on TODO list for next release get done, and that developers just don't
>    work on cool features they want that may not match TODO list
Well, the best method of dealing with this I've seen, is with how many
projects set things like "Blocking 2.0" in their bugzilla system. We
might be able to use either categories or priority with the sf.net
tracker, however that seems hackish to me and wouldn't be the clearest.
That said, I think if we are to continue using the sf.net tracker, it
would be best to use that for TODO goals, however I think it may be
worth considering moving off of sf.net for bug tracking.

Alex Schultz