Git
Git is our preferred tool for code collaboration, with the Fudge source code projects available at github.com/FudgeMsg. The master branch contains the latest developments and may include functionality ahead of other implementations which therefore cannot be relied upon for interoperability. Branches will be made for key release points. Further commits to those branches will only be to correct any bugs specific to that release, never to add any additional functionality.
All commits to Git must include a JIRA reference (see below) in the comment, e.g. [FRJ-14] improved Javadoc comments.
Jira
Jira is our preferred bug and feature tracking tool available at jira.fugdemsg.org. If you discover any any faults with an implementation, see room for improvement or want to file a suggestion for improvement the Jira should be used. If you want to help with the coding, pick an outstanding issue from the Jira and join in! Although "TODO" and code review comments may be put in code during the development process, any such items must be moved to issues in the Jira before a release can be made.
When work is completed on a Jira issue, it should be marked as "resolved" and the resolution note to include a publicly visible repository, or branch on a repository, where the changes can be pulled from. Once the changes have been merged successfully into the master branch (or a legacy branch if it is an urgent bug fix) the issue will be closed.