atom feed15 messages in org.kde.kde-core-develKDE git workflow
FromSent OnAttachments
Cornelius SchumacherJun 8, 2011 10:03 am 
David JarvieJun 9, 2011 5:50 am 
Cornelius SchumacherJun 9, 2011 6:33 am 
Maksim OrlovichJun 9, 2011 6:57 am 
Torgny NyblomJun 9, 2011 9:13 am 
Cornelius SchumacherJun 9, 2011 9:22 am 
Cornelius SchumacherJun 9, 2011 9:34 am 
David JarvieJun 9, 2011 9:35 am 
Cornelius SchumacherJun 9, 2011 9:39 am 
John LaytJun 9, 2011 9:56 am 
Cornelius SchumacherJun 9, 2011 2:32 pm 
Aaron J. SeigoJun 9, 2011 3:15 pm 
Ben CooksleyJun 9, 2011 6:55 pm 
John LaytJun 13, 2011 2:53 am 
Alexander NeundorfJun 13, 2011 4:40 am 
Subject:KDE git workflow
From:Cornelius Schumacher (
Date:Jun 8, 2011 10:03:01 am

As you already know, we have discussed the git workflow for KDE at the Platform 11 sprint, and have come up with a recommendation. Please find the full text here:

The core ideas are that: * master is always kept in a stable state that is ready to be used for starting a release * development is happening in feature branches * for larger projects integration branches will be used for further stabilization and wider testing * changes going into master are going through a review process * releases are coming from release branches

Please read the full text before commenting to get all details.

This workflow will be adopted by some core modules, and is recommended for all KDE modules. It's flexible enough to be used by modules of different sizes and different requirements in terms of stability, so we hope it to be a reasonable fit for as many people as possible. Obviously we'll have to see how well it works and adapt it, if necessary, but it should be a good start.