Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-mysqlbackend
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
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
Code review analytics
Issue 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
caosdb
Software
caosdb-mysqlbackend
Commits
610020bb
Verified
Commit
610020bb
authored
1 year ago
by
Timm Fitschen
Browse files
Options
Downloads
Patches
Plain Diff
DOC: update RELEASE_GUIDELINES
parent
534b67be
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!11
DRAFT: file system cleanup
Pipeline
#42844
failed
1 year ago
Stage: test
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
RELEASE_GUIDELINES.md
+8
-3
8 additions, 3 deletions
RELEASE_GUIDELINES.md
with
8 additions
and
3 deletions
RELEASE_GUIDELINES.md
+
8
−
3
View file @
610020bb
...
@@ -19,10 +19,15 @@ guidelines of the CaosDB Project
...
@@ -19,10 +19,15 @@ guidelines of the CaosDB Project
2.
Check all general prerequisites.
2.
Check all general prerequisites.
3.
Assure that the latest patch actually updates the CaosDBVersion() procedure
and that the version matches the version you are about to release.
4.
Merge the release branch into the main branch.
4.
Merge the release branch into the main branch.
5.
Tag the latest commit of the main branch with
`v<VERSION>`
.
5.
Wait for the main branch pipeline to pass.
6.
Tag the latest commit of the main branch with
`v<VERSION>`
.
6
.
Delete the release branch.
7
.
Delete the release branch.
7
.
Merge the main branch back into the dev branch.
8
.
Merge the main branch back into the dev branch.
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