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

Get rid of manager-release branch support in testing framework (SCT, DTest) #4043

Open
mikliapko opened this issue Sep 25, 2024 · 1 comment
Assignees
Labels
qa should be used for qa team testing tasks

Comments

@mikliapko
Copy link

Currently, we are supporting two branches in two testing frameworks used for Manager testing (SCT, DTest):

  • master;
  • manager-release (manager-3.3 currently).

Since I started working with Manager test about half a year ago, we have never encountered a case where there were test-specific differences between these two branches. At the same time, manager-release branch support takes time on backporting and conflicts resolution.

To sum it up, I see no reason to support both of them and suggest to stay with only one master branch.

If there's a need for a separate release branch, we can create it any time.

@mikliapko mikliapko added refinement-needed qa should be used for qa team testing tasks labels Sep 25, 2024
@mikliapko mikliapko self-assigned this Sep 25, 2024
@karol-kokoszka
Copy link
Collaborator

We are not really backporting fixes from master to branches other than the current release.
It makes sense to get rid of manager-release branch in SCT and Dtest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa should be used for qa team testing tasks
Projects
None yet
Development

No branches or pull requests

2 participants