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.

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

Consider adding an "On Hold" label #10

Open
jsf9k opened this issue Dec 18, 2020 · 5 comments
Open

Consider adding an "On Hold" label #10

jsf9k opened this issue Dec 18, 2020 · 5 comments
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use

Comments

@jsf9k
Copy link
Member

jsf9k commented Dec 18, 2020

🚀 Feature Proposal

We should consider adding an "On Hold" label that is distinct from the "Blocked" label. See the discussion in cisagov/skeleton-generic#63. It may even make sense to create both an "On Hold" label and a more specific "Waiting for Kraken" label.

Motivation

When we are holding back a PR because we are waiting to gather enough PRs for a Kraken release, the PR is not "blocked" per se. There are also other cases where we might put a PR on hold even though it is not actually blocked by anything else, although perhaps the concept of a draft PR covers this case.

The advantage of creating a more specific "Waiting for Kraken" label is that we can easily do a search for it and thus identify all PRs that should be merged when it is time to release the Kraken.

@jsf9k jsf9k added the improvement This issue or pull request will add or improve functionality, maintainability, or ease of use label Dec 18, 2020
@hillaryj
Copy link
Contributor

This sounds good - I propose adding two labels:

  • on hold for things that are on hold for whatever reason but not blocked by something external
  • kraken or lineage-kraken to indicate things that are kraken-ready

Examples:

  • A PR that is on hold awaiting a coordinating PR would be labelled on hold
  • A PR that is ready but awaiting the next Lineage kraken release would be labelled on hold kraken

@hillaryj
Copy link
Contributor

hillaryj commented Dec 18, 2020

My proposed labels (available in this repository):
Screen Shot 2020-12-18 at 12 12 36 PM

kraken: This pull request is ready to merge during the next Lineage kraken release
on hold: This pull request is awaiting an action like another pull request or a Lineage kraken release

@jsf9k
Copy link
Member Author

jsf9k commented Dec 18, 2020

My proposed labels (available in this repository):
Screen Shot 2020-12-18 at 12 12 36 PM

kraken: This pull request is ready to merge during the next Lineage kraken release
on hold: This pull request is awaiting an action like another pull request or a Lineage kraken release

I don't think we should mention the Kraken in the description for the "on hold" label. That just muddies the water, and in that case we might as well just overload the "on hold" label (which I don't want to do).

Also, recall that our naming of the Kraken is a reference to "Clash of the Titans", where the Kraken is a particular beast and hence a proper noun; therefore, the word "Kraken" should be capitalized in the description for the "kraken" label.

@hillaryj
Copy link
Contributor

How about:

on hold: This pull request is awaiting an action or decision to move forward

@dav3r
Copy link
Member

dav3r commented Dec 21, 2020

I'm on board with adding the on hold and kraken labels. I also agree with @jsf9k's comment that we should capitalize Kraken wherever possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use
Projects
None yet
Development

No branches or pull requests

3 participants