Prioritized labels
Drag to reorder prioritized labels and change their relative priority.
Usage&Pragmatics
Simulation / OpenSCENARIO / OpenSCENARIO DSL
The group in the OSC 2.0 project that clusters the usage and pragmatics related WPs
-
Prioritized
- Issues
DomainModel
Simulation / OpenSCENARIO / OpenSCENARIO DSL
The group in the OSC 2.0 project that clusters the Domain Model related WPs
-
Prioritized
- Issues
Other labels
DomainModelAlignment
Simulation / OpenSCENARIO
A new feature for OSC 1.x which requires alignment of OSC 1.x, OSC 2.x domain models
isState:Accepted
Simulation
An issue that has been accepted by the group, which needs to be assigned to a responsible, given a due date and needs a clear specification of requirements to be fulfilled. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:Classified
Simulation
An issue that has a type and that needs to be accepted by the group. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:Implemented
Simulation
An issue that has a solution in an associated merge request, which is ready to be reviewed by the group. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:InProgress
Simulation
An issue that is assigned a responsible, has a due date and clear requirements, which now needs to be implemented in a solution. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:Integrated
Simulation
An issue that has been integrated and has an integration reviewer, which is ready to be checked and all open comments are resolved. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:New
Simulation
A new issue that needs to be classified to a type. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:ReadyForMerge
Simulation
An issue that has been integrated and is assigned to the workflow manager, which is ready to be merged. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isState:Reviewed
Simulation
An issue that has a been accepted by the group, has an assigned integrator, which is ready to be integrated into the standard or project. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.
isType:Bug
Simulation
An issue that contains contradictions or errors in the standard. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
isType:Editorial
Simulation
An issue that contains general structural and editorial changes for the whole documentation. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
isType:FeatureImprovement
Simulation
An issue that amends or improves existing features. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
isType:Infrastructure
Simulation
An issue related to the repository infrastructure such as CI, builds, document toolchain or similar. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
isType:MeetingMinutes
Simulation
An issue documenting meeting minutes for an ASAM meeting. On starting, a project shall define the location of all meeting minutes for the project. This is either in a project sharepoint or in the issue list. Meeting minutes should be kept for each official project meeting. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
isType:NewFeature
Simulation
An issue that adds new features to the project. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
isType:Question
Simulation
General questions about the project, work-flow or anything related to the standard as well as support requests. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.
resolutionType:Duplicate
Simulation
This issue has already been raised or was already solved in another issue. Resolution type labels indicate why an issue was closed. An issue must be closed to have a resolution and shall only have one resolution type.
resolutionType:Fixed
Simulation
The task described in the issue was addressed. Resolution type labels indicate why an issue was closed. An issue must be closed to have a resolution and shall only have one resolution type.
resolutionType:Rejected
Simulation
The task described in the issue will not addressed by this standard. Resolution type labels indicate why an issue was closed. An issue must be closed to have a resolution and shall only have one resolution type.
Prioritized