1 ===============================================================================
6 Do NOT commit to this module without permission from a maintainer;
7 see the MAINTAINERS file for who they are. You should also discuss any
8 changes on the gLabels developers mail list first:
10 glabels-devel@lists.sourceforge.net
12 To join the list visit:
14 https://lists.sourceforge.net/lists/listinfo/glabels-devel
16 The list is moderated for first time posters.
18 See below for additional guidelines.
24 Translation commits are always welcome. Please recognize any rules from
25 your local team of the GNOME Translation Project. You may add or change
33 Please don't edit the file POTFILES.in without approval from a
37 ===============================================================================
43 See the TODO file in this directory.
49 gLabels will typically have 2 active branches: a stable branch and a
50 development branch. A branch represents a series of releases with a
51 fixed major and minor version. The minor version will be an even
52 number for a stable branch and will be an odd number for a development
53 branch. For example the "2.2.5" release would be from a stable branch
54 and "2.3.5" would be a development release.
59 Some characteristics of a stable branch:
61 - Prerequisites are fixed for the lifetime of the branch.
62 - The primary purpose of releases within a branch is to fix bugs.
63 - Besides bug fixes, releases may also include new and updated translations,
64 updated documentation, and new label templates.
65 - Generally, no new features will be introduced by a release within a
66 stable branch unless it is necessary to fix a bug. Such a fix should not
67 introduce new prerequisites.
68 - Nor will code be refactored unless it is necessary to fix a bug.
69 - The Git branch will be named glabels_major_minor. E.g. "glabels_2_2".
71 Unstable/development branch
72 ---------------------------
74 Some characteristics of a development branch:
76 - Prerequisites are volatile and may change release to release.
77 - The primary purpose of releases is to introduce new features and
78 get them in the hands of testers.
79 - Features and file formats may be volatile and change release to
81 - No attempt will be made to maintain backwards compatibility with
83 - The development branch is maintained in the Git master branch.