Proposal for branching policy towards KF5

[David Faure]

On Saturday 20 July 2013 23:04:10 Michael Pyne wrote:
> Well there's a 3rd method as well, which is to add a separate metadata file
> to  the kde-build-metadata repository which maps each git repository to its
> appropriate branch for each of the 3 categories.

Sounds good to me.

> This is a labor-intensive task, but it's easy to centrally-manage without 
> having to rely on many different module maintainers or core developers for 
> each git repository to update their own metadata in projects.kde.org

I volunteer to help.

> (assuming  we can get the sysadmins to add that).

I didn't understand that. To add what?

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20130723/d9248e6c/attachment.sig>