For everything documentation-related

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 or Issues that add new API

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

Anything related to Universal Window Platform (UWP) support

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

Security related issues and MRs

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 the C# language bindings

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 unit tests and integration tests

Issues and merge requests related to the GStreamer validate framework

Issues and merge requests related to GStreamer libraries

Issues and merge requests related to any of the GStreamer plugins