developmentConventions

Release guide

This document presents some guidances for development, such as release cycle duration, sprints, naming, source code conventions.

Releases

A release is a functional prototype. A new prototype is released each month. This cycle is composed of 4 sprints (milestones), being 1 sprint/week.

Numbering & naming conventions:

• Release: Maritaca.VERSION.RELEASE.MILESTONE.BUGFIX

Where

• VERSION: Incremental number defined for the team (updated each 6 months approximately)
• Release: Incremental number of the Backlog update each month
• MILESTONE: Number between 1 to 4 identifying the sprint
• BUGFIX: Version number for bug fixes

Source code

Code is written in English

Commits

Every commit should begin with the following line:

Ticket: NUM, Status: STATUS

Where NUM is the number of the ticket related to the code being committed and STATUS is the status of that ticket after the commit. In the last commit during the development of a certain issue the status should be closed.

The valid status (retrieved from the source forge ticket system) are: open, unread, accepted, pending, closed and wont-fix.