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.

Sign up for GitHub

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

Jump to bottom

Add "Affects/v6" label to issues #321

Closed
GuySartorelli opened this issue Oct 10, 2024 · 2 comments
Closed

Add "Affects/v6" label to issues #321

GuySartorelli opened this issue Oct 10, 2024 · 2 comments
Labels
type/other

Comments

@GuySartorelli
Copy link
Member

GuySartorelli commented Oct 10, 2024 •
edited by emteknetnz
Loading

Now that we're a fair way into working on CMS 6, some issues we create will be for bugs or new features that only apply to CMS 6 branches of the various repositories.

The changes for these issues may not be API breaking changes in themselves, so the type/api-break label no longer covers all our bases for CMS 6 work.

Acceptance criteria

  • A "affects/v6" label is added to module standardiser
  • The new label is applied to all commercially supported repositories

PR
@emteknetnz emteknetnz self-assigned this Oct 23, 2024
@emteknetnz emteknetnz mentioned this issue Oct 23, 2024
Merged
@emteknetnz
Copy link
Member

Have run module-standardiser using PR branch and added affects/v6 label to all supported modules

@emteknetnz emteknetnz removed their assignment Oct 23, 2024
@GuySartorelli
Copy link
Member Author

PR merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/other
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@emteknetnz @GuySartorelli