5
5
please do as small commits to your local git tree, so there is a good
6
6
history of your changes.
8
When you consider changes ready for merging to mainline: host the repo somwhere
9
accessible with http and sumbit an enchancement bug to the dbus project in
10
http://bugs.freedesktop.org, notifying the mailing list.
8
When you consider changes ready for merging to mainline, either use
9
"git-format-patch" or otherwise generate diffs. Post those diffs
10
to a new bug at http://bugs.freedesktop.org, project DBus, component GLib.
13
For nontrivial changes *please* try to extend the test suite to cover it. The
14
test infrastructure is in test/core/, and currently there are a lot of tests
15
in the single file test/core/test-dbus-glib.c. Extending this file is
16
suggested (in the future we would like to break this file up).
18
Run "make check" to run the test suite.
22
DBus-Glib now uses an even-stable odd-development release numbering
23
system. The current number in configure.ac should be odd.
29
* edit configure.ac, change version to even (e.g. 0.75 -> 0.76)
33
* git commit -m "Release"
34
* scp resulting tarball to ssh://gabe.freedesktop.org/srv/dbus.freedesktop.org/releases/dbus-glib
35
* edit configure.ac, change version to odd (e.g. 0.76 -> 0.77)
36
* git commit -m "Bump version for development"
37
* Update the wiki: http://www.freedesktop.org/wiki/Software/DBusBindings
38
* Announce the release on the mailing list