|
|
| (21 intermediate revisions by 12 users not shown) |
| Line 1: |
Line 1: |
| == Guidelines ==
| | {{Moved To Community}} |
| === Think Twice before Committing ===
| |
| Committing something to SVN has serious consequences. All other developers will get your changes once they are in SVN, and if they break something, they will break it for everybody. All commits will be publicly available in the SVN repository forever.
| |
| | |
| On the other hand SVN allows one to revert changes, so it's possible to recover from mistakes. This is relatively easy for commits to single files but it can also be a significant amount of work for bigger changes.
| |
| The baseline is: Be aware of the consequences of your commits. Take time to think about them before committing.
| |
| | |
| === Never commit code that doesn't compile ===
| |
| Compile the code and correct all errors before committing. Make sure that newly added files are comitted. If they are missing your local compile will work fine but everybody else won't be able to compile.
| |
| | |
| You certainly should make sure that the code compiles with your local setup. You should also consider what consequences your commit will have for compiling with the source directory being different from the build directory. It would also be nice if it would compile with the <code>--enable-final</code> option, but we don't explicitly support that.
| |
| | |
| Be especially careful if you change the build system, i.e. Makefiles
| |
| | |
| === Test your changes before committing ===
| |
| Start the application affected by your change and make sure that the changed code behaves as desired.
| |
| | |
| Run regression tests if available (<code>make check</code>).
| |
| | |
| === Double check what you commit ===
| |
| Do a <code>svn update</code> and a <code>svn diff</code> before committing. Take messages from SVN about conflicts, unknown files, etc. seriously. ''svn diff'' will tell you exactly what you will be committing. Check if that's really what you intended to commit.
| |
| | |
| === Always add descriptive log messages ===
| |
| Log messages should be understandable to someone who sees only the log. They shouldn't depend on information outside the context of the commit. Try to put the log messages only to those files which are really affected by the change described in the log message.
| |
| | |
| In particular put all important information which can't be seen from the diff in the log message.
| |
| | |
| === Honor KDE coding policies ===
| |
| This includes security (shell quoting, buffer overflows, format string vulnerabilities), binary compatibility (d pointers), i18n, usability, user interface style guide, (API) documentation, documentation and definition of memory management and ownership policies, method naming, conditions for inclusion in kdelibs, portability issues and license notices.
| |
| | |
| These policies are defined separately. If in doubt ask on the mailing list.
| |
| | |
| === Respect commit policies set by the Release Plans ===
| |
| | |
| === Respect other developer's code ===
| |
| Respect the policies of application and library maintainers, and consult with them before making large changes.
| |
| | |
| Source control systems are not a substitute for developer communication.
| |
| | |
| === Announce changes in advance ===
| |
| When you plan to make changes which affect a lot of different code in SVN, announce them on the mailing list in advance. For instance, changes in libraries might break other code even if they look trivial, e.g., because an application must also compile with older versions of the librariy for some reasons. By announcing the changes in advance, developers are prepared, and can express concerns before something gets broken.
| |
| | |
| === Code review by other developers ===
| |
| Don't commit changes to the public API of libraries without prior review by other developers. There are certain special requirements for the public APIs of the KDE libraries, e.g., source and binary compatibility issues. Changes to the public APIs affect many other KDE developers including third party developers, so requiring a review for these changes is intended to avoid problems for the users of the APIs and to improve the quality of the APIs.
| |
| | |
| === Take responsibilty for your commits ===
| |
| If your commit breaks something or has side effects on other code, take the responsibility to fix or help fix the problems.
| |
| | |
| === Don't commit code you don't understand ===
| |
| Avoid things like "I don't know why it crashes, but when I do this, it does not crash anymore." or "I'm not completely sure if thats right, but at least it works for me.".
| |
| | |
| If you don't find a solution to a problem, discuss it with other developers.
| |
| | |
| === Don't commit if other developers disagree ===
| |
| If there are disagreements over code changes, these should be resolved by discussing them on the mailing lists or in private, not by forcing code on others by simply committing the changes to SVN.
| |
| | |
| === Backport bugfixes ===
| |
| If you commit bugfixes, consider porting the fixes to other branches. Use the same comment for both the original fix and the backport, that way it is easy to see which fixes have been backported already.
| |
| | |
| === Use bug tracking system numbers ===
| |
| If you fix bugs reported on the bug tracking system, add the bug number to the log message. In order to keep the bug tracking system in sync with SVN, you should reference the bug report in your commits, and close the fixed bugs in the bug tracking system.
| |
| | |
| This doesn't mean that you don't need an understandable log message. It should be clear from the log message what has been changed without looking at the bug report.
| |
| | |
| === Tags and branches ===
| |
| There are rules for where to place release tags and branches in the repository. Official KDE branches and release will be created by the release KDE coordinator in the <code>branches/KDE</code> and <code>tags/KDE</code> directories, scripts will ensure that this folders are protected.
| |
| | |
| Developers should place all branches which are aimed to be released in <code>branches/appname</code> and name them like the release, e.g. <code>branches/appname/1.5</code>. For all release tags, <code>tags/appname</code> is the right place.
| |
| | |
| All temporary working branches (which should be deleted again after the work has ended) should be located in <code>branches/work</code> with some name describing both which part of KDE (or which application) is branched and which work is done there. A good example would be <code>branches/work/khtml-paged</code> for a khtml working branch to include paged media support. Bad idea would be something like <code>branches/work/make-it-cool</code>.
| |
| | |
| === Don't add generated files to the repository ===
| |
| Files generated at build time shouldn't be checked into the repository because this is redundant information and might cause conflicts. Only real source files should be in SVN. An exception to that are files generated by tools that would be an unusual requirement for building KDE.
| |
| | |
| Standard tools include autoconf/automake, gcc, bash, perl, moc, uic and the tools part of KDE itself, e.g. dcopidl.
| |
| | |
| Tools which shouldn't be a requirement for building KDE include lex/flex, yacc/bison, python, ruby etc.
| |
| | |
| === Don't use SVN keywords in source files ===
| |
| SVN keywords like <code>Id</code> or <code>Log</code> cause unnecessary conflicts when merging branches and don't contain any information which wouldn't be available in the SVN repository anyway.
| |
| | |
| === Make "atomic" commits ===
| |
| SVN has the ability to commit more than one file at a time. Therefore, please commit all related changes in multiple files, even if they span over multiple directories at the same time in the same commit. This way, you ensure that SVN stays in a compileable state before and after the commit.
| |
| | |
| === Don't mix formatting changes with code changes ===
| |
| Changing formatting like indenting or white spaces blows up the diff, so that it is hard to find code changes if they are mixed with reindenting commits or similar things when looking at the logs and diffs later. Committing formatting changes separately solves this problem.
| |
| | |
| === GUI Changes ===
| |
| If your commit causes user visible GUI changes, add the <code>GUI</code> keyword to the log message. This makes sure that the documentation writers get notified of your changes.
| |
| | |
| == Special keywords in SVN log messages ==
| |
| When you commit changes to SVN you will be asked for a description of your commit. There are several special keywords defined that you can use in this description. These keywords are always uppercase and followed by a colon. Each keyword should be placed on a line of its own. The following keywords can be used.
| |
| * '''BUG:''' ''<bugnumber>''<br/>Marks the bug as closed by CC'ing the commit message to <bugnumber>[email protected] This keyword will also be used to automatically extract entries for the release changelog. | |
| * '''CCBUG:''' ''<bugnumber>''<br/>CC's to the bugreport by sending mail to <bugnumber>@bugs.kde.org
| |
| * '''CCMAIL:''' <email-address><br/>CC's to the given e-mail address.
| |
| * '''SVN_SILENT:'''<br/>Marks the commit message "silent" by adding "(silent)" to the subject of the mail to allow filtering out trivial commits. Use this tag carefully and only for really uninteresting, uncontroversial commits.
| |
| * '''FEATURE:''' [''<bugnumber>'']<br/>Marks the feature as implemented by CC'ing the commit message to <bugnumber>[email protected]. This keyword will also be used to automatically extract entries for the release changelog, so it makes sense to use it for new features even if you don't have a bugnumber for the feature. | |
| * '''GUI:'''<br/>Indicates a user visible change in the user interface. This is used to make the documentation team aware of such changes.
| |
| | |
| == Contact ==
| |
| | |
