Labels
Prioritized labels 2
Drag to reorder prioritized labels and change their relative priority.
-
priorityKeyQuantifyThis issue/MR is key for the associated milestone and must be completed before the deadline of the milestone. Some will be associated with a milestone without this label because they are not blocking the release (e.g. external feature contributions).
-
priorityCriticalQuantifyThis issue has critical priority and must be worked on ASAP to go into a hotfix release (if necessary). Git cherry-pick or file checkout can be used for this.
Other labels 41
-
ComponentBackend KeysightQuantify / quantify-schedulerRelated to the quantify-scheduler keysight hardware backend.
-
ComponentCompilationQuantifyRelated to the compilation of a schedule from the gate to pulse level, or pulse to backend level.
-
ComponentControlQuantifyRelated to the control of experiment, e.g. measurement control, settables and gettables, etc..
-
ComponentDocsQuantifyRelated to the documentation, its building, RTD, docstrings, tutorials, etc..
-
ComponentInfrastructureQuantifyRelated to aspects not strictly related to code, e.g., problems with CI, GitLab workflow, non-code issues, etc..
-
MR State1. In progress...Quantify[Progress captain: assignee] MR not ready for complete review. Equivalent to Draft/WIP. The assignee is responsible for asking help/advice by tagging relevant people. Next state: "2. Review me!".
-
MR State2. Review me!Quantify[Progress captain: assignee] MR was submitted and is ready for review. Assignee may tag potential reviewers in the comments. Next state: "3. In review...".
-
MR State3. In review...Quantify[Progress captain: reviewer] A reviewer with enough expertise is reviewing the MR (the reviewer should self-assign as such). If there are no concerns so far and the reviewer does not have enough expertise, the "2. Review me!" label should be activated again. Next state: "4. Change requested" or "5. Merge me!".
-
MR State4. Change requestedQuantify[Progress captain: assignee] Reviewer's comments need to be addressed (comments/code/test/docs/etc.). Conflict with target branch should be addressed carefully. Next state: "2. Review me!".
-
MR State5. Merge me!Quantify[Progress captain: assignee & maintainer] MR ready to be merged. Assignee should tag maintainers. Next state: Merged or "4. Change requested".
-
New issueQuantifyNew issue that just got created -- flag it so it can be reviewed/follow-up defined by maintainers
-
RequestDiscussion in DMQuantifyThis is requested to be discussed in a coming weekly Developers Meeting.