« Previous - Version 7/65 (diff) - Next » - Current version
Nils Kredens, 08/23/2013 09:45 am


Ticket categories definition

  • Development : development tasks
  • Administration: portal administration interface and tools (Portal project)
  • Commands: any command related issue (all projects)
  • Conventions: algorithms and terminology conventions (all projects)
  • Documentation: any documentation issue (manuals, wikis, web pages...) (SH: Javadoc?)
  • Import: any import module issue
  • Preferences: RCP preferences issues
  • Setup: desktop RCP setup issues
  • Stats: statistic models issues
    • Stats / R: R related statistic models issues
  • Toolbox: any issue related to the Toolbox project
  • UI: User Interface issues in the RCP project (SH: and GWT project?)
    • UI / Interaction: user interface behavior issues
    • UI / Link / Command: user interface hypertextual command behavior issues

Ticket status cycle

The classic ticket status cycle:

New -> In Progress -> Feedback -> Resolved

  • New: the ticket concerns a demand not yet started
  • In Progress: the demand is currently treated
  • Feedback: the solution is tested and awaits the other users and developers feedback
  • Resolved: the solution is approved and is deployed throughout the application

Other status that can occur at any time in the development:

  • Closed: the demand is no longer treated (eg. abandon)
  • Rejected: concerns a new demand which is not to be treated

SVN commit messages

Each entry of the message :
  • is prefixed with RCP: or TBX: or WEB: or DOC: or <plugin name>:
  • then insert the nature of the commit for example : "add", "fix" ...
  • and insert the details
  • if you need more than one line to describe the entry, prefix the following lines with "#"

Example:

TBX: add an awesome new functionnality
TBX: fix the XXX import module
# the flow was not Groovy enough
# end of this entry
DOC: add documentation of the new functionnality

For further information about commit syntax, you can go on this page

https://github.com/erlang/otp/wiki/Writing-good-commit-messages