Skip to content
Vlad Dumitrescu edited this page Oct 27, 2010 · 1 revision

Development process

Prev

Chapter 3. Developer reference


Development process

Source code management

Repository structure

The source code is stored in a Subversion repository. We use a standard structure, where the Eclipse project directories lie directly under the trunk:

                /

                branches/

                RB_x/

                org.erlide.*

                tags/

                REL_y/

                org.erlide.*

                trunk/

                org.erlide.*

This way, we can do a checkout on the whole trunk directly in a workspace directory. This will allow to do atomic commits across all projects by using an external svn client, because from within Eclipse the atomicity is per project (a limitation of the Eclipse plugins).

Branches

  • The trunk will contain the bleeding edge of development, but it should be buildable at any time.

  • Release branches will be named RB-x.x

  • Larger features should be implemented in separate branches.

Commit policies

To be specified.

Testing

We strive to add both unit tests and "sanity" tests (the latter ones should check that a build is somewhat sane and didn't mess up anything basic).


Prev

Up

Plugin description

Home

Clone this wiki locally