Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release process enhancements #3891

Merged
merged 3 commits into from
Apr 29, 2021
Merged

Release process enhancements #3891

merged 3 commits into from
Apr 29, 2021

Conversation

tjanez
Copy link
Member

@tjanez tjanez commented Apr 27, 2021

No description provided.

@tjanez tjanez added the c:ops Category: operations label Apr 27, 2021
```

### Back-port Changes

Create a new branch, e.g. `<GITHUB-NAME>/${RELEASE_BRANCH}/backport-foo`, from
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm I think we should still namespce the changes by user, similar as we do for regular branches.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is a fair point. I was balancing the need for namespacing and having copy & paste Release Process docs.

My internal reasoning for not bothering with namespacing is that these branches (backport and changelog branches) should typically be short-lived and deleted automatically.

@tjanez tjanez force-pushed the tjanez/release-process-enh branch from 2194153 to b9ece53 Compare April 29, 2021 15:36
@tjanez tjanez merged commit 55f2484 into master Apr 29, 2021
@tjanez tjanez deleted the tjanez/release-process-enh branch April 29, 2021 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:ops Category: operations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants