1 GNOME Utilities HACKING
3 Please send patches to any of the people listed in the MAINTAINERS file
4 or, alternatively, attach them to a bugzilla.gnome.org report.
6 Features that require a patchset or discussion are to be sent to the
7 gnome-utils mailing list for review.
9 If you want to implement a complex feature you can request a branch
10 on the mailing list; the branch will be merged when the maintainers will
11 deem it ready. GNOME is using SVN which makes branches cheap, but
12 merging is still a pain; thus, what will be merged will not have a full
23 These branches are in deep code freeze. Please do not commit even the most
24 simple bug fixes to it without emailing the release team
25 release-team@gnome.org and MAINTAINERS, getting a confirmation of commit
26 from 2 release team members.
28 * Special notice for libgdict
30 Even though libgdict is not inside the Developers Platform, the same rules
31 (even if a bit more lax) apply to it:
33 - no ABI breaking, unless is absolutely unavoidable;
34 - no ABI/API breaking after ABI/API freeze;
35 - every API change must be *fully* documented;
37 If you intend to change the API for libgdict, contact Emmanuele Bassi (see
38 the MAINTAINERS file) and kindly provide a rationale for the API change,
39 with a use case and, possibly, a test case. In case of a patch (see above
40 for the diff format), kindly provide:
42 - documentation (in gtk-doc form);
45 The versioning scheme for libgdict should follow this ruleset:
47 if release is the first of a new development cycle:
50 else if release is before API freeze:
52 else if release is after API freeze: