Difference between revisions of "Subversion"
From OdaWiki
(→Guidelines) |
(→Guidelines) |
||
Line 35: | Line 35: | ||
** Mention related bugs and revisions (see [http://odamex.net/changelog changelog] for format) | ** Mention related bugs and revisions (see [http://odamex.net/changelog changelog] for format) | ||
** Seek comments on bugzilla and forum before making major changes | ** Seek comments on bugzilla and forum before making major changes | ||
+ | ** Test your changes before every commit | ||
* Do not | * Do not | ||
** Commit broken code to trunk or stable | ** Commit broken code to trunk or stable | ||
** Commit untested code to stable | ** Commit untested code to stable | ||
− | ** | + | ** Make giant monolithic commits |
− | + | ||
** Make major changes without consulting maintainers | ** Make major changes without consulting maintainers | ||
** Make frivolous commits | ** Make frivolous commits | ||
+ | ** Overwrite other people's recent work without asking them |
Revision as of 16:19, 13 April 2006
SubVersion is the current version control repository used to maintain the odamex source code. Access is restricted based on our Policy.
Tested clients
- svn
- tortoisesvn for Windows
Directory structure
Each branch keeps an entire odamex source tree.
- root
- trunk - bleeding edge development, may not always work
- branches
- stable - synchronised with trunk when features mature
- ogl_hack - a half-hearted attempt at accelerating the renderer
- other temporary branches may be created or destoryed
- tags
Change notification
Any changes to our svn repository are reported in:
Guidelines
- Do
- Regularly update your working copy
- Commit individual improvements and corrections to the existing code
- Separate your commits semantically
- Make an informative comment with each commit
- Mention related bugs and revisions (see changelog for format)
- Seek comments on bugzilla and forum before making major changes
- Test your changes before every commit
- Do not
- Commit broken code to trunk or stable
- Commit untested code to stable
- Make giant monolithic commits
- Make major changes without consulting maintainers
- Make frivolous commits
- Overwrite other people's recent work without asking them