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

Removed multitest_api_1_0 feature #71

Merged
merged 1 commit into from
Sep 27, 2023

Conversation

DariuszDepta
Copy link
Member

Using a dedicated feature to plan API changes in future version is more cumbersome than keeping issues to be implemented before releasing planned version. As an example, see: #69 and #70.

@DariuszDepta DariuszDepta self-assigned this Sep 26, 2023
Copy link
Contributor

@jawoznia jawoznia left a comment

Choose a reason for hiding this comment

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

Agree. This introduces a lot of noise in the code. I would much more prefer smaller releases with breaking changes allowing users to adapt in time.

No approve as I would prefer that someone who has better insight in cw-multi-test release plan to make the decision.

Copy link
Contributor

@hashedone hashedone left a comment

Choose a reason for hiding this comment

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

LGTM

@DariuszDepta DariuszDepta merged commit 5a17c7e into main Sep 27, 2023
2 checks passed
@DariuszDepta DariuszDepta deleted the remove-multitest-api-1-0-feature branch September 27, 2023 08:47
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

Successfully merging this pull request may close these issues.

3 participants