Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
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
-
Issues or Merge Requests that should be revisited after the next major release
-
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.
-
Label for MRs that are good to be merged once the git repository is no longer frozen
-
Merge Requests that were successfully backported to the stable 1.14 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.18 branch
-
Issues and merge requests related to language bindings and GObject Introspection
-
Issues and merge requests related to Python language bindings and GStreamer Python overrides (gst-python)
-
Issues and merge requests related to the Rust language bindings and Rust plugins
-
Issues and merge requests related to GStreamer tools such as gst-launch, gst-inspect, gst-play, gst-device-monitor, etc.
-
Issues and merge requests related to the GStreamer validate framework
Prioritized