3 GLib is the low-level core library that forms the basis for projects such
4 as GTK and GNOME. It provides data structure handling for C, portability
5 wrappers, and interfaces for such runtime functionality as an event loop,
6 threads, dynamic loading, and an object system.
8 The official download locations are:
9 <https://download.gnome.org/sources/glib>
11 The official web site is:
12 <https://www.gtk.org/>
16 See the file '[INSTALL.md](INSTALL.md)'
20 Only the most recent unstable and stable release series are supported. All
21 older versions are not supported upstream and may contain bugs, some of
22 which may be exploitable security vulnerabilities.
24 See [SECURITY.md](SECURITY.md) for more details.
28 API documentation is available online for GLib for the:
29 * [GLib](https://docs.gtk.org/glib/)
30 * [GObject](https://docs.gtk.org/gobject/)
31 * [GModule](https://docs.gtk.org/gmodule/)
32 * [GIO](https://docs.gtk.org/gio/)
36 If you have a question about how to use GLib, seek help on [GNOME’s Discourse
37 instance](https://discourse.gnome.org/tags/glib). Alternatively, ask a question
38 on [StackOverflow and tag it `glib`](https://stackoverflow.com/questions/tagged/glib).
42 Bugs should be [reported to the GNOME issue tracking system](https://gitlab.gnome.org/GNOME/glib/issues/new).
43 You will need to create an account for yourself. You may also submit bugs by
44 e-mail (without an account) by e-mailing <incoming+gnome-glib-658-issue-@gitlab.gnome.org>,
45 but this will give you a degraded experience.
47 Bugs are for reporting problems in GLib itself, not for asking questions about
48 how to use it. To ask questions, use one of our [discussion forums](#discussion).
50 In bug reports please include:
52 * Information about your system. For instance:
53 * What operating system and version
54 * For Linux, what version of the C library
55 * And anything else you think is relevant.
56 * How to reproduce the bug.
57 * If you can reproduce it with one of the test programs that are built
58 in the `tests/` subdirectory, that will be most convenient. Otherwise,
59 please include a short test program that exhibits the behavior.
60 As a last resort, you can also provide a pointer to a larger piece
61 of software that can be downloaded.
62 * If the bug was a crash, the exact text that was printed out
63 when the crash occurred.
64 * Further information such as stack traces may be useful, but
67 ## Contributing to GLib
69 Please follow the [contribution guide](./CONTRIBUTING.md) to know how to
70 start contributing to GLib.
72 Patches should be [submitted as merge requests](https://gitlab.gnome.org/GNOME/glib/-/merge_requests/new)
73 to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the
74 issue in your commit message with the following notation (for issue 123):
79 Otherwise, create a new merge request that introduces the change. Filing a
80 separate issue is not required.
82 ## Default branch renamed to `main`
84 The default development branch of GLib has been renamed to `main`. To update
85 your local checkout, use:
88 git branch -m master main
90 git branch --unset-upstream
91 git branch -u origin/main
92 git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main