-
Notifications
You must be signed in to change notification settings - Fork 1.7k
README: replace Testify V2 notice with @dolmen's V2 manifesto #1518
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
README: replace Testify V2 notice with @dolmen's V2 manifesto #1518
Conversation
hi! maybe it's better not to remove, but (in contradict) notice about v2 manifesto? |
Yes, I think that's also a good idea. I'm thinking if maintainers want to link the manifesto instead I will just change the MR Lets wait his response maybe? |
Yes, linking to my manifesto would be better. |
f428650
to
b48f25e
Compare
Thanks for the answer, I have updated the readme with the manifesto |
@hendrywiranto also grep "testify v2" |
dac4a1b
to
d370c30
Compare
thanks for the reminder @Antonboom |
Hi, I am relatively new comer to the maintainers group for this, I mostly come from the opentelemetry collector contrib where I use this heavily, and also internally here at Altassian. As slow as it has been for V2 (apologies for those asking for it), I think it should be the ambition of 2024 to see v2 released. Let me follow up with @boyan-soubachov on this and we can start getting together a more formal roadmap / milestone for V2 if it doesn't already exist. |
I'm glad to hear that there is still plan for V2! Thanks! |
d370c30
to
3b4b536
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think there is a concensus about this between the maintainers right now. I'm not requesting any changes, just temporarily putting a hold on this.
I have proposed a different wording to expose the active debate about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I at least have changed my mind about testtify v2, that may mean there is now a concensus among the maintainers that it is a no.
README.md
Outdated
Notice about Testify V2: | ||
It won't happen due to various reasons. You can read more about it on the maintainer's manifesto [here](https://github.com/stretchr/testify/issues/1089#issuecomment-1812734472). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notice about Testify V2: | |
It won't happen due to various reasons. You can read more about it on the maintainer's manifesto [here](https://github.com/stretchr/testify/issues/1089#issuecomment-1812734472). | |
> [!NOTE] | |
> Testify is being maintained at v1, no breaking changes will be accepted in this repo. [See discussion about v2](https://github.com/stretchr/testify/discussions/1560). |
Suggest using a proper GitHub markdown note and remove the emotional language from the note.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @brackendawson
Thank you for finally coming to a concensus, I have applied your suggestion. 😄
50edd68
to
2780579
Compare
Summary
Remove Testify V2 notice on
README.md
since it won't happenChanges
README.md
Motivation
According to this announcement #1089 (comment) from @dolmen
Related issues
Issues that can be closed:
#1089