Skip to content

How to test the release#1198

Open
benoit-cty wants to merge 1 commit into
masterfrom
docs/test_release_how_to
Open

How to test the release#1198
benoit-cty wants to merge 1 commit into
masterfrom
docs/test_release_how_to

Conversation

@benoit-cty
Copy link
Copy Markdown
Contributor

Small addition to contributing.md to explain how to test a fresh release.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

AI Usage Disclosure

Please refer to docs/how-to/ai-policy.md for detailed guidelines on how to disclose AI usage in your PR. Accurately completing this section is mandatory.

  • 🟥 AI-vibecoded: You cannot explain the logic. Car analogy : the car drive by itself, you are outside it and just tell it where to go.
  • 🟠 AI-generated: Car analogy : the car drive by itself, you are inside and give instructions.
  • ⭐ AI-assisted. Car analogy : you drive the car, AI help you find your way.
  • ♻️ No AI used. Car analogy : you drive the car.

@benoit-cty benoit-cty requested a review from a team as a code owner May 17, 2026 13:41
@benoit-cty benoit-cty added the documentation Improvements or additions to documentation label May 17, 2026
Copy link
Copy Markdown
Collaborator

@inimaz inimaz left a comment

Choose a reason for hiding this comment

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

Thanks @benoit-cty! For this and the release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants