Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
otb
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sébastien Peillet
otb
Commits
62f1f7fa
Commit
62f1f7fa
authored
7 years ago
by
Guillaume Pasero
Browse files
Options
Downloads
Patches
Plain Diff
DOC: add some guidelines for gitlab
parent
7cee3883
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+18
-0
18 additions, 0 deletions
CONTRIBUTING.md
with
18 additions
and
0 deletions
CONTRIBUTING.md
+
18
−
0
View file @
62f1f7fa
...
...
@@ -127,3 +127,21 @@ OTB source code. Under some conditions (dependencies, official acceptance
process, etc.), we are also able to distribute your remote module in the
official standalone binaries. See
[
the wiki
](
https://wiki.orfeo-toolbox.org/index.php/Remote_Modules
)
for more information.
## Gitlab guidelines
In order to organize the issues in our Gitlab instance, we use both labels and
milestones.
The
[
milestones
](
https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/milestones
)
should be used to track in which release a feature is merged.
Gitlab can then provide a summary of all features and bugs added to a given release
version.
Regarding labels, we use the following set:
*
~story: significant feature to be implemented with a detailed work plan, it can
correspond to a Request for Comments that has turned into a development action
*
~bug: Bug, crash or unexpected behavior, reported by a user or a developer
*
~feature: Feature request expressed by an OTB user/developer
*
~"To Do": action is planned
*
~Doing: work in progress
*
~api ~app ~documentation ~monteverdi ~packaging ~qgis: optional context information
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment