Difference between revisions of "Redmine"
Luca.frosini (Talk | contribs) (→Introduction) |
Luca.frosini (Talk | contribs) |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | Redmine is an open source, web-based project management and issue-tracking tool. | + | Redmine is an open source, web-based project management and issue-tracking tool. Redmine allows hyper-linking information between a ticket, revision control and wiki content. It also serves as a web interface to Version Control Systems (e.g. SVN, git). |
D4Science infrastructure provide an instance of Redmine with a dedicated project for gCube tracking issues available at [https://support.d4science.org/projects/gcube https://support.d4science.org/projects/gcube] | D4Science infrastructure provide an instance of Redmine with a dedicated project for gCube tracking issues available at [https://support.d4science.org/projects/gcube https://support.d4science.org/projects/gcube] | ||
| + | |||
| + | The D4Science Redmine instance supports AGILE methodology support. In brief the development process is divided in '''Milestone'''. The target of a Milestone lead to a new gCube release. Inside each Milestone the work is mainly divided in '''sprints'''. A sprint isa a colelction of related action to reach a goals. A sprint should not have a duration of more than 2 week and never more than a month. | ||
| + | A sprint can be be the list of actions needed to add a new functionality to a software component, the tasks related to release a new version and so on. | ||
== gCube Redmine Project == | == gCube Redmine Project == | ||
| − | Redmine is used to trigger new activities to do in gCube software, to react to defects found in candidate releases of gCube System, and to manage release procedures (such as start of releases, attach subsystem configurations). | + | Redmine is used to trigger new activities to do in gCube software, to answer to support requests, to react to defects found in candidate releases of gCube System, and to manage release procedures (such as start of releases, attach subsystem configurations). |
| + | |||
| + | The gCube project provide different tickets types (tracker in Redmine terminology) to provide a clear view of the gCube Software system status. Each tracker can have different fields and different status. To be compliant with AGILE methodology each task must belong to one Sprint. | ||
| + | |||
| + | |||
| + | === Feature === | ||
| + | |||
| + | Used to define a task to do do to accomplish the objective of the '''sprint''' it belongs to. | ||
| + | |||
| + | === Bug === | ||
| + | |||
| + | Used to keep track of a malfunction of a software component (a bug) or a problem in the release process. | ||
| + | |||
| + | === Support === | ||
| + | |||
| + | Used to request support regarding the use of a software component. So that, it can be used by a developer to request more information about using a particular library developed by another one, or by an end-user regarding how to do something in an user interface. | ||
| + | |||
| + | Before opening this type of ticket everyone MUST be sure that a similar ticket does not already exist. After each request of support each developers should take actions to avoid that others can have the same troubles (e.g. improve Javadoc, improve wiki documentations and so on). | ||
| + | |||
| + | === Release === | ||
| − | + | Used during release cycle to keep track of subsystem and related components to be released. | |
Revision as of 12:53, 4 September 2015
Introduction
Redmine is an open source, web-based project management and issue-tracking tool. Redmine allows hyper-linking information between a ticket, revision control and wiki content. It also serves as a web interface to Version Control Systems (e.g. SVN, git).
D4Science infrastructure provide an instance of Redmine with a dedicated project for gCube tracking issues available at https://support.d4science.org/projects/gcube
The D4Science Redmine instance supports AGILE methodology support. In brief the development process is divided in Milestone. The target of a Milestone lead to a new gCube release. Inside each Milestone the work is mainly divided in sprints. A sprint isa a colelction of related action to reach a goals. A sprint should not have a duration of more than 2 week and never more than a month. A sprint can be be the list of actions needed to add a new functionality to a software component, the tasks related to release a new version and so on.
gCube Redmine Project
Redmine is used to trigger new activities to do in gCube software, to answer to support requests, to react to defects found in candidate releases of gCube System, and to manage release procedures (such as start of releases, attach subsystem configurations).
The gCube project provide different tickets types (tracker in Redmine terminology) to provide a clear view of the gCube Software system status. Each tracker can have different fields and different status. To be compliant with AGILE methodology each task must belong to one Sprint.
Feature
Used to define a task to do do to accomplish the objective of the sprint it belongs to.
Bug
Used to keep track of a malfunction of a software component (a bug) or a problem in the release process.
Support
Used to request support regarding the use of a software component. So that, it can be used by a developer to request more information about using a particular library developed by another one, or by an end-user regarding how to do something in an user interface.
Before opening this type of ticket everyone MUST be sure that a similar ticket does not already exist. After each request of support each developers should take actions to avoid that others can have the same troubles (e.g. improve Javadoc, improve wiki documentations and so on).
Release
Used during release cycle to keep track of subsystem and related components to be released.
