KDE Commit Policy

[Thiago Macieira]

Cornelius Schumacher wrote:
>It should be replaced by the corresponding rule we use for tags and
>branches in SVN.
>
>I'm not sure what our policies for tags and branches in SVN actually
>are. The existing ones are a bit confusing. Could somebody explain what
>our policy is meant to be?

The current policy is enforced by ACL rules, so there's no need to write 
them as guidelines. Namely, each application has a subdir in branches & 
tags, and only the sysadmins and release dudes have write access to 
branches/KDE and tags/KDE.

Moreover, there's branches/work which is free for anyone to use, provided 
you erase it after you're done using.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

5. Swa he géanhwearf tó timbran, and hwonne he cóm, lá! Unix cwæð "Hello, 
World". Ǽfre ǽghwilc wæs glæd and seo woruld wæs fréo.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050925/b97390e4/attachment.sig>