Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Move ignition issues to the ignition repo #2471

Closed
5 tasks done
ashcrow opened this issue Jul 2, 2018 · 11 comments
Closed
5 tasks done

Move ignition issues to the ignition repo #2471

ashcrow opened this issue Jul 2, 2018 · 11 comments

Comments

@ashcrow
Copy link
Member

ashcrow commented Jul 2, 2018

Feature Request

Desired Feature

Other Information

ignition has been undergoing work so that it has the ability to be used in multiple distributions. Currently all bugs for ignition fall under this repository. While that made a lot of sense when ignition was specific to Container Linux/original CoreOS I believe it is a bit confusing as we widen out ignition usage.

If this move sounds good I'll help make it happen :-)

@ashcrow
Copy link
Member Author

ashcrow commented Jul 2, 2018

/cc @cgwalters @bgilbert @crawford

@lucab
Copy link

lucab commented Jul 2, 2018

I left a similar comment for coreos-metadata at #2468 (comment) this morning.

@crawford
Copy link
Contributor

crawford commented Jul 2, 2018

🚢 🇮🇹

@ashcrow
Copy link
Member Author

ashcrow commented Jul 2, 2018

@crawford that took me a minute 😆

@ashcrow
Copy link
Member Author

ashcrow commented Jul 2, 2018

In repo doc update: coreos/ignition#572

@ashcrow
Copy link
Member Author

ashcrow commented Jul 2, 2018

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 ignition repository.

@ashcrow
Copy link
Member Author

ashcrow commented Jul 2, 2018

In the meantime, let's talk labels. I'm keen to keep area/* labels as well as the default GitHub labels. Is there any other labels we need to bring along besides those?

@bgilbert
Copy link
Contributor

bgilbert commented Jul 2, 2018

@ashcrow Need? No. But IMO kind/*, platform/*, and needs/* (or equivalent) would be useful here. Is there value to keeping the default labels in their unprefixed form?

@ashcrow
Copy link
Member Author

ashcrow commented Jul 3, 2018

@bgilbert I've generally used them myself. However, if we want to specifically move to kind/* instead of the default, then no we don't need them.

@bgilbert
Copy link
Contributor

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.

@bgilbert
Copy link
Contributor

I think this is all done now, for both Ignition and coreos-metadata. Closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants