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
Add task groups to the Plugin API #677
Conversation
|
Warning: Issue #6414 is not at NEW/ASSIGNED/POST. |
|
I thought this over and I think we need a new issue that we can add to a 3.3.1 milestone plus changelog entry that will show up in the 3.3.1 changelog. |
|
The changelog entry that already went out in 3.3.0 already mentions "plugin writers", so it arguably doesn't need a changelog entry. wdyt? Here's what it says:
|
|
If #6414 were unreleased (and at MODIFIED) then I think it would be ok. My understanding of our release process though is that we can't/shouldn't attach changes to released issues. |
593ff5c
to
ecdee6f
Compare
This is also my understanding. An issue can't be fixed in two releases. Additionally it creates issues for any downstream during their cherry picking process. |
Somehow this never got added to the plugin API even though I remember making the change, it must have gotten accidentally stashed or something. There's already a changelog entry... we can send this out in a Y release.
re: #6414
https://pulp.plan.io/issues/6414