blob: e28820332019e6ec23b464bcd80fb71a65ac8582 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
# Project
If you want to create a fork and use an external account (Github, Google) drop us a message at the Gajim support [group chat](xmpp:gajim@conference.gajim.org?join) so we can give you the necessary rights
## Versioning
┌────── Major (Will not change unless we switch GTK version)
│ ┌───── Minor (Changes when new features are introduced
│ │ ┌──── Micro (Used for hotfixes and small changes)
│ │ │ ┌─── Only used while developing
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
1.3.3-dev1
## Branches
Currently there is only one stable/development branch - master.
The master branch must always be in a releasable state.
Development for bigger changes need to happen in feature branches or forks.
Previously the project maintained multiple versions of Gajim in
different stable branches, but from Gajim 1.4.0 on this approach was changed
to lower the maintenance burden and release faster.
# Commit Messages
If you are not familiar with Git please read the [HowTo](https://dev.gajim.org/gajim/gajim/wikis/development/howtogit)
A good article regarding [good commit messages](https://chris.beams.io/posts/git-commit/)
Every commit message must be prefixed with one of the following tags:
- ci (ci related changes)
- feat (functionality of the application was changed)
- fix (something was fixed)
- perf (performance related changes)
- refactor (code was changed, but the end user will not notice)
- chore (reoccuring tasks which need to be done)
- other
Further the first letter after the tag must be upper case
Example:
`feat: New Button which does something`
|
