Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Tatuya Kamada
gitlab-ce
Commits
33dbb30f
Commit
33dbb30f
authored
May 22, 2015
by
Job van der Voort
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
notify the core team and devs
parent
f5db97aa
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
1 deletion
+4
-1
doc/release/monthly.md
doc/release/monthly.md
+4
-1
No files found.
doc/release/monthly.md
View file @
33dbb30f
...
@@ -9,7 +9,8 @@ The new release manager should create overall issue to track the progress.
...
@@ -9,7 +9,8 @@ The new release manager should create overall issue to track the progress.
## Release Manager
## Release Manager
A release manager is selected that coordinates all releases the coming month, including the patch releases for previous releases.
A release manager is selected that coordinates all releases the coming month,
including the patch releases for previous releases.
The release manager has to make sure all the steps below are done and delegated where necessary.
The release manager has to make sure all the steps below are done and delegated where necessary.
This person should also make sure this document is kept up to date and issues are created and updated.
This person should also make sure this document is kept up to date and issues are created and updated.
...
@@ -93,6 +94,8 @@ There are three changelogs that need to be updated: CE, EE and CI.
...
@@ -93,6 +94,8 @@ There are three changelogs that need to be updated: CE, EE and CI.
Once the stable branches have been created, update the CHANGELOG in
`master`
with the upcoming version, usually X.X.X.pre.
Once the stable branches have been created, update the CHANGELOG in
`master`
with the upcoming version, usually X.X.X.pre.
On creating the stable branches, notify the core team and developers.
## QA
## QA
Create issue on dev.gitlab.org
`gitlab`
repository, named "GitLab X.X QA" in order to keep track of the progress.
Create issue on dev.gitlab.org
`gitlab`
repository, named "GitLab X.X QA" in order to keep track of the progress.
...
...
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