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

Mechanism to open and close branches #2463

Closed
Tracked by #2447
jcagme opened this issue Feb 27, 2020 · 4 comments
Closed
Tracked by #2447

Mechanism to open and close branches #2463

jcagme opened this issue Feb 27, 2020 · 4 comments

Comments

@jcagme
Copy link
Contributor

jcagme commented Feb 27, 2020

We need a mechanism so we can open new branches when is time to start a new release and close the old branches when they are not needed anymore. This in the effort of fully automate the prep and release process

@jcagme jcagme changed the title Mechanism to open and close branches [Build ring] Mechanism to open and close branches Mar 9, 2020
@jcagme jcagme changed the title [Build ring] Mechanism to open and close branches [Release prep] Mechanism to open and close branches Mar 9, 2020
@Tohron Tohron self-assigned this Mar 11, 2020
@jcagme jcagme changed the title [Release prep] Mechanism to open and close branches [QCR][Release prep] Mechanism to open and close branches Mar 12, 2020
@jcagme
Copy link
Contributor Author

jcagme commented Apr 8, 2020

This is related #2462

@jcagme
Copy link
Contributor Author

jcagme commented Jul 16, 2020

Un-assigning @Tohron since he is working on something else now

@michellemcdaniel
Copy link
Contributor

michellemcdaniel commented Apr 22, 2021

Out of scope for dotnet/arcade#6418.

Async Triage: we may need a new bucket/epic for release-ish related work items that are out of scope for Shipping With Confidence.

@michellemcdaniel michellemcdaniel changed the title [QCR][Release prep] Mechanism to open and close branches Mechanism to open and close branches Apr 22, 2021
@dkurepa dkurepa transferred this issue from dotnet/arcade Jun 2, 2023
@dkurepa dkurepa added this to the Improve Release Process milestone Jun 2, 2023
@andriipatsula
Copy link
Member

Closing this as the issue is almost 4 years old and we don’t have plans to work on this in the near future. In case you believe the issue needs resolution - please reopen it and provide a reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants