-
Notifications
You must be signed in to change notification settings - Fork 59
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
templates/rebase: add instructions for creating tracker tickets #1220
templates/rebase: add instructions for creating tracker tickets #1220
Conversation
.github/ISSUE_TEMPLATE/rebase.md
Outdated
## At previous Fedora major release | ||
|
||
### Open tickets to track related work for this release | ||
|
||
- [ ] Fedora Changes Considerations [example](https://github.com/coreos/fedora-coreos-tracker/issues/918) | ||
- [ ] Package Additions/Removals [example](https://github.com/coreos/fedora-coreos-tracker/issues/1128) | ||
- [ ] Test Week [example](https://github.com/coreos/fedora-coreos-tracker/issues/1123) |
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.
Could we do this at the end of the checklist instead for the next rebase? (I.e. put it under the "Open ticket for the next Fedora rebase" section.)
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 started with them down there but then moved them up here. I decided to do that because it's nicer to be able to fire off and create a single ticket (that has a full template) than it is to do these other tickets (require a little more thought). i.e. someone can finish the previous release easily. These other tickets can get picked up later (they are tracked at least).
5e80f5c
to
00fbe69
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.
LGTM
These tickets help us stay up on various release processes and changes. Let's formalize them in our toplevel rebase tracker template.
00fbe69
to
554d045
Compare
These tickets help us stay up on various release processes and
changes. Let's formalize them in our toplevel rebase tracker template.