DRAFT

[sethulakshmi-pm]

Why

What

References

• Story / Card
• Support Case
• Backend Card or PR
• Backend PR to pick up weasel
• UI-Client Card or PR
• Release Notes task or PR
• Documentation card or PR
• Loadgenerator card or PR

Checklist

• A new version of weasel?
  • Add this feature into CHANGELOG.md
  • Increase version in package.json
  • Tag main branch with new version after the PR is merged
• API change?
  • API Documentation is updated in JavaScript Agent API page
• Test is needed?
  • Unit test case is applied to cover code change
  • End to end test case is applied to cover code change
• User facing change?
  • A card or PR for backend is created and linked in references
  • A card or PR for Ui-Client is created and linked in references
  • A sub-task or PR for Release Notes is created and linked in references
  • A card or PR for loadgenerator is created and linked in reference
  • An item is added in release testing card
• Documentation needs an update?
  • Docs PR is created and linked in references

Merge Guidance

❗ Please use a squash merge unless there is an explicit reason you need to use a different merge strategy (e.g. you are bringing in changes from a previous release branch, or you have specific changes in your branch that you would like to retain). This keeps our commit history clean, makes changes more atomic, and makes it easier to revert changes.