KDE Commit Policy

[Christoph Cullmann]

On Monday 26 September 2005 08:45, Sascha Cunz wrote:
> you probably don't know that kdevelop will release an additional version
> after the one shipped with kde3.5.
>
> While trunk/KDE/kdevelop is for KDE4 (Will be released as KDevelop 4.0) and
> branches/KDE/3.5/kdevelop is for KDE 3.5 (Will be released as KDevelop 3.3
> with KDE3.5), branches/work/kdevelop3 is the development line for KDevelop
> 3.x and will be released as KDevelop 3.4 after KDE 3.5 has long been out.
>
> However, i agree that the branch-name "kdevelop3" cannot be understood
> without the above knowledge. Can you suggest a "better name"?
Hmm, but than this branch will be released which makes it no temporary working 
branch :/ It should have been some branches/kdevelop/3.6 or whatever branch 
which stays alive even after the release, while stuff in branches/work should 
be deleted after the work is done ;)
Btw., shouldn't some branches in branches/kdevelop put to rest? 2 and 1.4 I 
understand, but are make_kdevelop_cool, fast_editor_branch and 
annotation_devel_branch are not old working branches?

But back to the Policy, is everybody OK to add the following stuff:

16. Developers should place their temporary working branches (which should be 
deleted again after the work has ended) in branches/work 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 branches/work/khtml-paged 
for a khtml working branch to include paged media support. All branches which 
are aimed to be released later should be placed in branches/<appname> and be 
named like the release, like branches/arts/1.5. For alle release tags, 
tags/<appname> is the right place.

cu
Christoph