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

Write up how we want to do tags and feature branches #5259

Closed
teor2345 opened this issue Sep 26, 2022 · 2 comments · Fixed by #5392
Closed

Write up how we want to do tags and feature branches #5259

teor2345 opened this issue Sep 26, 2022 · 2 comments · Fixed by #5392
Assignees
Labels
A-consensus Area: Consensus rule updates A-docs Area: Documentation C-enhancement Category: This is an improvement

Comments

@teor2345
Copy link
Contributor

teor2345 commented Sep 26, 2022

Motivation

We want to document the process we decided for new features. We also want to write down the goals we're trying to satisfy.

The draft notes are in the Retrospective pad.
We've also had some conversations in Slack about how this could work.

@teor2345 teor2345 added A-docs Area: Documentation A-consensus Area: Consensus rule updates C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage P-Medium ⚡ labels Sep 26, 2022
@mpguerra
Copy link
Contributor

@mpguerra mpguerra removed the S-needs-triage Status: A bug report needs triage label Oct 19, 2022
@teor2345 teor2345 changed the title Write up how we want to do audit tags, audit branches, and feature branches Write up how we want to do tags and feature branches Oct 19, 2022
@teor2345
Copy link
Contributor Author

The audit tag and branch part got split into ticket #5431 and PR #5395.

@mergify mergify bot closed this as completed in #5392 Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-consensus Area: Consensus rule updates A-docs Area: Documentation C-enhancement Category: This is an improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants