From 5c1676dfe6d2f3c837a5e074117b45613fd29a72 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 20:30:19 +0200 Subject: Adding upstream version 2.10.34. Signed-off-by: Daniel Baumann --- devel-docs/gitlab-milestones.txt | 41 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 devel-docs/gitlab-milestones.txt (limited to 'devel-docs/gitlab-milestones.txt') diff --git a/devel-docs/gitlab-milestones.txt b/devel-docs/gitlab-milestones.txt new file mode 100644 index 0000000..6ea285a --- /dev/null +++ b/devel-docs/gitlab-milestones.txt @@ -0,0 +1,41 @@ +gitlab-milestones.txt +----------------------- + +This document describes how the GIMP project uses milestones in the +GNOME gitlab issue tracker found at: +https://gitlab.gnome.org/GNOME/gimp + + +Stable milestone +---------------- + +The bugs on a stable milestone, e.g. on the 2.8 milestone if GIMP +2.8 is the stable release, are bugs for which fixes will be accepted +onto the stable branch. + +Reports for bugs that are fixed in the stable branch should have the +stable milestone set. Usually such a fix is done in the development +branch and then cherry-picked to the stable branch. + + +Next stable milestone +--------------------- + +The bugs/enhancement requests on the next stable milestone, e.g. on +the 2.10 milestone if GIMP 2.8 is the stable release, are bugs or +enhancement requests scheduled and planned for inclusion in the next +stable version. This list is rather dynamic and will be altered during +the execution of a development cycle. + +If you fix a bug or implement a feature request for the next release, +then please make sure that the milestone is set accordingly. This +allows us to make a list of changes by looking at the resolved bugs on +the milestone. + + +Future milestone +---------------- + +The bugs/enhancement requests on the Future milestone are things that +the GIMP project eventually want to include in a future version, but +in what version is not yet decided. -- cgit v1.2.3