Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
Bugs for things that worked fine in previous versions and thus need to be fixed with high priority
-
Merge Requests that were successfully backported to the stable 1.18 branch
-
Issues and merge requests reported against or relating to a 1.18 version or branch
-
Merge Requests that were successfully backported to the stable 1.16 branch
-
Merge Requests that were successfully backported to the stable 1.14 branch
-
Label for MRs that are good to be merged once the git repository is no longer frozen
-
Use this label to tag Merge Requests that are not release relevant and should not be milestoned (e.g. "back to dev" type commits or commits that have subsequently been reverted). This is used by release scripts.
-
Issues or Merge Requests that should be revisited after the next major release
-
Merge requests that should maybe be backported to the latest stable branch, but for now we defer that decision. Ideally also add the appropriate stable branch label, e.g. 1.16
-
Merge requests that should be backported to the latest stable branch. Ideally also add the appropriate stable branch label, e.g. 1.16
-
Issues relating to plugins and libraries that are to be moved from one GStreamer module to another
-
Performance-related issues (mostly CPU performance, for memory usage use the Memory tag)
Prioritized