Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
aparapi-docker
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
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
Aparapi
aparapi-docker
Commits
184c3906
Commit
184c3906
authored
4 years ago
by
Jeffrey Phillips Freeman
Browse files
Options
Downloads
Plain Diff
Merge branch 'develop' into 2.0.0
parents
36b66ffb
c3fbf3d5
No related branches found
No related tags found
No related merge requests found
Pipeline
#658
passed with stage
Stage:
in 1 minute and 58 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+3
-3
3 additions, 3 deletions
CONTRIBUTING.md
with
3 additions
and
3 deletions
CONTRIBUTING.md
+
3
−
3
View file @
184c3906
...
...
@@ -91,9 +91,9 @@ Next lets take a few steps to do the actual release:
7.
If pipeline passed, create a generic new branch, do not push it, as follows
`git checkout -b release`
.
8.
Update the pipeline badge in the readme to point to the to-be-released repository tag/version.
9.
Commit the current changes using a generic commit message such as
`build(release): version 1.2.3 revision 4`
. But do not push.
10.
Create a new tag for the current revision with the following command:
`git tag -a
v
1.2.3-4 -m "Version 1.2.3 revision 4"`
. Ensure
tags
**always**
have the aparapi version followed by revsion.
11.
Push the newly created tag to the server:
`git push origin
v
1.2.3-4:
v
1.2.3-4`
.
10.
Create a new tag for the current revision with the following command:
`git tag -a 1.2.3-4 -m "Version 1.2.3 revision 4"`
. Ensure
tags
**always**
have the aparapi version followed by revsion
and never have the letter
`v`
prepending it
.
11.
Push the newly created tag to the server:
`git push origin 1.2.3-4:1.2.3-4`
.
12.
Delete the release branch you created locally
`git branch -D release`
.
13.
If the Aparapi version deployed is the latest then merge develop branch into master, develop branch should already contain latest
Aparapi version from the first step.
...
...
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