Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
otb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
273
Issues
273
List
Boards
Labels
Service Desk
Milestones
Merge Requests
8
Merge Requests
8
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Main Repositories
otb
Commits
62f1f7fa
Commit
62f1f7fa
authored
Feb 14, 2018
by
Guillaume Pasero
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
DOC: add some guidelines for gitlab
parent
7cee3883
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
18 additions
and
0 deletions
+18
-0
CONTRIBUTING.md
CONTRIBUTING.md
+18
-0
No files found.
CONTRIBUTING.md
View file @
62f1f7fa
...
@@ -127,3 +127,21 @@ OTB source code. Under some conditions (dependencies, official acceptance
...
@@ -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
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
)
official standalone binaries. See
[
the wiki
](
https://wiki.orfeo-toolbox.org/index.php/Remote_Modules
)
for more information.
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
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment