* Developing for CEDET

** Repository layout

   The main repositories are:

   - =www= :: Web page contents.
   - =code= :: Cedet-related code.

   The /code/ repository is organized in a set of branches:

   - =code/trunk= :: Main development branch.
   - =code/cedet-<version>= :: Branch for the given major release. Minor
        releases are identified by tags.
   - Any other branch is for in-development features (see below).

** Workflow key points

   This workflow is very strict and can seem like unnecessarily complicated for
   those who think version control is just a necessary evil. The fact is that
   sticking to a single workflow like this one will (hopefully) ease the
   management of the project.

   - Every new feature is developed on its own branch.

   - If the feature takes a relatively long time to develop or multiple
     developers must collaborate, it can be published (=push=) on the cedet
     repository or elsewere (sourceforge provides its users with the ability to
     publish branches on their own repositories).

   - Those without access to the repository For relatively small 

   - Once the feature has been tested, the feature branch is merged into trunk
     with a message naming and describing the feature. Once merged, the feature
     branch can be simply deleted.

   - In the case of bugfixes, these must also be developed on their own
     branch. Of course, a bugfix for a non-merged branch is developed on the
     non-merged branch.

   - A set of well-known developers will manually pick up commits from trunk and
     transplant them to the release branches (=code/cedet-<version>=) if they
     see fit in order to provide new minor releases.

   - *Never* commit directly into a release branch

   - *Never* merge from a release branch into =trunk=

   This workflow is based on
   http://www.emacswiki.org/emacs/BzrForEmacsDevs#toc16

** Links

   - SourceForce repository URLs
     https://sourceforge.net/scm/?type=bzr&group_id=17886
     You must login to see URLs for read/write acess 

   - SourceForge-specific information when using bazaar
     https://sourceforge.net/apps/trac/sourceforge/wiki/Bazaar
     *NOTE*: It is very important to correctly set /whoami/

   - A quick peek on a very similar workflow, describing all the commands
     http://www.emacswiki.org/emacs/BzrForEmacsDevs
     Change URLs and developer info with that provided on previous links. The
     workflow described in this document supersedes the one described on the
     given link.