The ASAM GitLab will be unavailable in the week of the 12th to the 16th of December for essential maintenance. All content, including issues and remote repositories will not be accessible.

Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
  • isType:UML
    This label indicates that the issue deals with an UML related topic. Type labels display the intended field of the issue. Type labels are static and never change. (Old label name: UML)
  • requires:CCBReview
    This label indicates that the concept of this issue and a matching merge request is ready for review by the CCB. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: NeedsCCBReview)
  • requires:Clarification
    This label indicates that this issue needs a clarification by an expert. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: needsClarification)
  • requires:ConceptualWork
    This label indicates that this issue needs conceptual work by an expert or an expert group. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: needsClarification)
  • requires:DocumentationWork
    This label indicates that this issue needs a change of the documentation which has to be implemented by a project member. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: Documentation (Editorial Changes))
  • requires:Example
    This label indicates that the issue needs an example to illustrate or test a section in the document which has to be implemented by a project member. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed.
  • requires:Merge
    This label indicates that this issue or a merge request is approved by the CCB and should be merged by a project member with the necessary rights. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: ReadyToMerge)
  • requires:MergeRequest
    This tag indicates that this topic has a concise concept that is ready to be implemented in a merge request (either in the form of technical documentation, writing code, or model development). Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: Implementation)
  • requires:Test
    This label identifies tasks that need to be tested before they can be closed or the next step can be taken. This could be done with an example. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed.