== Guidelines ==
=== Honor KDE coding policies ===
...
14 KB (2,277 words) - 16:49, 28 November 2023
...that, and if no one steps in to reject, they are accepted per KDE's global policies
...kdereview means that the game is working fine and compliant to all quality guidelines, but not necessarily that it's an interesting and worthwhile new game.
...
48 KB (7,132 words) - 12:47, 27 March 2012
Guidelines and best practices for applying this policy can be found in the [[Guideline
All new source code and related data files in KDE repositories (SVN, Git) must meet the following requirements:
...
16 KB (2,463 words) - 08:08, 11 January 2023
Guidelines and best practices for applying this policy can be found in the [[Guideline
All new source code and related data files in KDE repositories (SVN, Git) must meet the following requirements:
...
16 KB (2,463 words) - 15:21, 31 December 2022
12:07: <_CitizenKane_> and knowledge of SVN in some cases
12:09: <Jucato> Socceroos_home: the kde website itself is maintained through SVN, with commit hooks
...
84 KB (12,829 words) - 11:04, 28 July 2010
[20:29:13] <eean> well feature branches always happen. in the previous svn model people would just keep the work on their computer much of the time
...ate them from actual integration/release branches? (like /branches/work in svn?)
...
140 KB (20,916 words) - 21:39, 15 February 2011
