Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Dunitrust
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
nodes
rust
Dunitrust
Commits
2802edac
Commit
2802edac
authored
7 years ago
by
nanocryk
Browse files
Options
Downloads
Patches
Plain Diff
[enh] Detailed merge process
parent
ed578b79
No related branches found
No related tags found
1 merge request
!12
Resolve "Write contributing doc"
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+23
-9
23 additions, 9 deletions
CONTRIBUTING.md
with
23 additions
and
9 deletions
CONTRIBUTING.md
+
23
−
9
View file @
2802edac
...
...
@@ -85,9 +85,23 @@ Please note we have a specific workflow, please follow it in all your interactio
1.
Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
2.
Update the README.md with details of changes to the interface, this includes new environment
1.
Ensure you rebased your branch on the latest
`dev`
commit to avoid any merge conflicts.
1.
Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
3.
Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is
[
SemVer
](
http://semver.org/
)
.
4.
You may merge the Merge Request in once you have the sign-off of two other developers, or if you
1.
Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is
[
SemVer
](
http://semver.org/
)
:
If the create is in developement stage, its format is 0.X.Y. In production stage, it's X.Y.Z.
- When a API breaking change is made, X must be incremented.
- If new features are added without breaking the API, Y must be incremented.
- If the change is a quick fix of a production version, Z is incremented.
Your crate should always start with 0.1.0 version and only pass in 1.0.0 when no big changes are
planned. There is no need to rush a 1.0.0, take your time :)
1.
You may merge the Merge Request in once you have the sign-off of two other developers. If you
do not have permission to do that, you may request the second reviewer to merge it for you.
\ No newline at end of file
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