Skip to content
Snippets Groups Projects

Add HIGH_PROFILE explanation

Merged Keita Kawabe requested to merge RapidResponse_HighProfile into main

Description

Fixes #389 (closed).

Added an explanation about HIGH_PROFILE label in vetting.rst as well as glossary. Added a line to change log.

Checklist

Thanks for your contribution! Please complete and check off the following quality control tasks.

Changes:

  • I created this merge request from my own fork and from a branch other than main or master.
  • I checked that the CI pipeline completes without errors (except for linkcheck).
  • I added a change log entry (or this is a minor change that does not require a change log entry).

Whitespace:

Grammar and spelling:

Figures and code:

  • I contributed plot directive code to generate figures (or I did not contribute any figures).
  • I contributed Python code that conforms to the PEP 8 style guide (or I did not contribute Python code).
Edited by Leo Pound Singer

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
    • Resolved by Leo Pound Singer

      I am worried that this text may be a bit hard to follow because we have so many similar-sounding concepts: high profile events, significant events, preferred events. Is there anything that you can do to clarify the relationship between these concepts?

  • Keita Kawabe resolved all threads

    resolved all threads

  • Keita Kawabe added 1 commit

    added 1 commit

    Compare with previous version

  • Leo Pound Singer
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading