-
Notifications
You must be signed in to change notification settings - Fork 30
Move ignition issues to the ignition repo #2471
Comments
I left a similar comment for coreos-metadata at #2468 (comment) this morning. |
🚢 🇮🇹 |
@crawford that took me a minute 😆 |
In repo doc update: coreos/ignition#572 |
We had a bit of a false start on this. It sounds we are in agreement to do this, but we have different views on how much needs to happen right away. I'll follow up with an email thread to try to get some of that hammered out before we continue. In the mean time issues have been turned off in the |
In the meantime, let's talk labels. I'm keen to keep |
@ashcrow Need? No. But IMO |
@bgilbert I've generally used them myself. However, if we want to specifically move to |
Issues have been re-enabled in the Ignition repo and upstream issues have been migrated from coreos/bugs. (Downstream Container Linux integration bugs should still be tracked in coreos/bugs.) The issue template PR is up at coreos/ignition#595. |
I think this is all done now, for both Ignition and coreos-metadata. Closing. |
Feature Request
Desired Feature
issues
area under ignitionignition
issues to https://github.com/coreos/ignition/issuesOther Information
ignition
has been undergoing work so that it has the ability to be used in multiple distributions. Currently all bugs forignition
fall under this repository. While that made a lot of sense whenignition
was specific to Container Linux/original CoreOS I believe it is a bit confusing as we widen outignition
usage.If this move sounds good I'll help make it happen :-)
The text was updated successfully, but these errors were encountered: