Skip to content

History / Issue Labels

Revisions

  • Link from old Issue-Labels page to new page

    @billsacks billsacks committed Jul 10, 2019
    f9e9992

  • Rename Issue-Labels to Issue-Labels-and-Issue-Management

    @billsacks billsacks committed Jul 10, 2019
    31ef682

  • Add "tag: next" label This was Negin's idea, which I like

    @billsacks billsacks committed Jun 14, 2019
    401392b

  • Remove lilac tag Now using a project for this

    @billsacks billsacks committed Jun 14, 2019
    cc440f2

  • Add 'tag: blocker' label

    @billsacks billsacks committed Jun 14, 2019
    e293884

  • For issue triage, can also add 'good first issue' tag

    @billsacks billsacks committed Jun 14, 2019
    7b4b576

  • Rename tag

    @billsacks billsacks committed Jun 13, 2019
    82ed6b9

  • add link

    @billsacks billsacks committed Jun 13, 2019
    12a6e99

  • Tweak wording

    @billsacks billsacks committed Jun 13, 2019
    e2ff810

  • Fix internal link

    @billsacks billsacks committed Jun 13, 2019
    5a96396

  • Tweak search for issues to triage, and add notes about triaging issues

    @billsacks billsacks committed Jun 13, 2019
    c4fd0e6

  • Use standard language for blocking

    @billsacks billsacks committed Jun 12, 2019
    047dd89

  • Add 'blocked: dependency' label

    @billsacks billsacks committed Jun 12, 2019
    eb9dea9

  • Add a note

    @billsacks billsacks committed May 24, 2019
    fb6f88e

  • Document reworked issue labels Reworked issue labels as per https://github.com/ESCOMP/ctsm/issues/730 Also added some helpful starting points for issue searches

    @billsacks billsacks committed May 24, 2019
    e7a18aa

  • Move some issue labels to a different section `docs - non-code` and `support tools` DO require code changes

    @billsacks billsacks committed May 10, 2019
    17302e0

  • Document the 'blocked: answer changing' issue label

    @billsacks billsacks committed Mar 12, 2019
    c2fc6d3

  • Document new issue label, "tag: lilac"

    @billsacks billsacks committed Jan 28, 2019
    d23da98

  • Updated Issue Labels (markdown)

    @ekluzek ekluzek committed Jan 18, 2019
    e6fdacb

  • Updated Issue Labels (markdown)

    @ekluzek ekluzek committed Jan 18, 2019
    cbf7a20

  • Updated Issue Labels (markdown)

    @ekluzek ekluzek committed Jan 18, 2019
    70f0cd0

  • Organize issue labels

    @billsacks billsacks committed Nov 7, 2018
    44689c7

  • Change 'status' prefix to 'closed' We'll use the status prefix for PRs

    @billsacks billsacks committed Sep 21, 2018
    a89a426

  • Add label: "type: tests"

    @billsacks billsacks committed Jun 14, 2018
    598dfe7

  • Tweak the distinction between 'code cleanup' and 'enhance - software' The old definitions (based on whether there is any potential behavior change) were leading me to put some issues in the "enhance - software" category that really felt like they should belong in the "code cleanup" category: e.g., issues which were really about code cleanup, but it was some large code cleanup that might change answers. Putting myself in the shoes of Dave or another manager, I felt like the important distinction is: What is the primary purpose – adding functionality or improving the internal code structure.

    @billsacks billsacks committed Feb 14, 2018
    536fc8e

  • Merge 'docs - code' into 'code cleanup' 'docs - code' doesn't seem to deserve its own label

    @billsacks billsacks committed Feb 13, 2018
    5015291

  • Clarify 'enhance - software' Even a *potential* change in behavior qualifies for this label as opposed to 'code cleanup'

    @billsacks billsacks committed Feb 9, 2018
    3ce1180

  • Clarify difference between some types Clarify difference between 'enhance - science', 'enhance - software' and 'code cleanup'

    @billsacks billsacks committed Feb 9, 2018
    04de8c9

  • Separate the bug label into two Distinguish between whether a bug affects the scientific results or not. Motivation: It can be useful to see at a glance what known bugs there are that can cause incorrect results.

    @billsacks billsacks committed Feb 8, 2018
    2b830bb

  • code cleanup = refactoring

    @billsacks billsacks committed Feb 8, 2018
    db40ee0