Spawend desktop_client_patch_release_template.md from the release_template.md #7674
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Copied to #7651 |
TheOneRing
reviewed
Jan 17, 2020
| ### After QA Approval | ||
|
|
||
| * [ ] DEV: remove git suffix "2.6.1git" -> "2.6.1" in [`VERSION.cmake`](https://handbook.owncloud.com/release_processes/client/branch.html#version-cmake) - @TheOneRing @guruz | ||
| * [ ] On branch sprint-1 add the release tag v2.6.1 |
There was a problem hiding this comment.
Not sure what this line is supposed to say
There was a problem hiding this comment.
Changed to: On sprint branch create a signed tag v2.6.1 using git tag -u E94E7B37 tagname
|
Closing this now, if this is still relevant... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
from https://etherpad.owncloud.com/p/patch-template
This already includes the manual cleanup that I promised after closing the meeting.
@guruz @TheOneRing Proofreading needed.
@HanaGemela should that go into handbook later, or now?
I suggest we start the 2.6.1 release issue with this template and backport changes from the release ticket to the template when the release is done.