gwenview/devdoc/CONTRIBUTING.md

0001 # Intro
0002
0003 Great to hear you want to contribute to Gwenview! Patches are always welcome.
0004
0005 # Mailing list
0006
0007 If you want to discuss development of Gwenview, you can subscribe to
0008 gwenview-devel mailing list:
0009 <https://mail.kde.org/mailman/listinfo/gwenview-devel>.
0010
0011 # Bug tracker
0012
0013 Gwenview bugs are tracked on KDE Bugzilla (<http://bugs.kde.org>). They are
0014 assigned to a fake user by default: `gwenview-bugs-null@kde.org`. To get
0015 notified when new bugs are filed, add this user to the list of users you follow.
0016 You can do so from Bugzilla by editing your user preferences, then go in the
0017 "Email Preferences" tab (<https://bugs.kde.org/userprefs.cgi?tab=email>)
0018
0019 # Code review
0020
0021 Patches should be sent for review on <http://git.reviewboard.kde.org>. You will
0022 get faster answers by posting them there rather than attaching them to a
0023 Bugzilla bug report.
0024
0025 # Commits for stable branch
0026
0027 Commits to stable branch should be made to the stable branch first, then merged
0028 back to master.
0029
0030 Here is an example work-flow.
0031
0032 First fix something in KDE/4.x:
0033
0034     git checkout KDE/4.x
0035     # Fix something, get it reviewed
0036     git commit
0037     git push
0038
0039 Now merge the commit in master. Note the use of `--no-ff` in `git merge`. This
0040 is required to make it easy to rollback the merge if need be.
0041
0042     git checkout master
0043     git merge --no-ff origin/KDE/4.x
0044     # Check merge is correct
0045     git push