Git Workflow - Outstanding Issues

Alexander Neundorf neundorf at
Sun May 15 16:54:31 BST 2011


On Friday 18 March 2011, John Layt wrote:
> Hi,
> We still have some outstanding issues from the Git Workflow meeting a while
> back (see which I'd
> like to see updated.
> * Workflow
> eean, steveire and PovAddict were to draw up alternative workflow
> proposals, steveire has drawn up one at
> (see earlier
> thread).  Do we have the other proposals yet?  What needs doing to move
> this forward?

Any progress here ?
AFAIK we still haven't decided on aynthing and have zero documentation.

I thought the ability to have better workflows with git was one of the 
motivations for the move to git.
Why aren't these better workflows documented or recommended anywhere ?

> * Release branch naming, KDE/4.6 vs 4.6
> This was decided by a coin toss to be 4.6 rather than KDE/4.6, but I
> suspect by now more people have stable branches from kdelibs/kdebase than
> the other modules so it may be less disruptive overall to use KDE/4.6?

Did we come to a conclusion about this in the latest thread ?
If so, which was it ?
This is also completely undocumented.
Git gurus, *please* work on that.
> Either way, there's still a couple of outstanding actions:
> ** Sysadmins to rename the branches that use the losing naming scheme if
> that's possible without too much disruption
> ** Sysadmins to block creating new branches for the losing naming scheme.
> * Documentation
> I've started the Git documentation:

I moved the "Creating a patch" link from "To be reviewed" to the "official" 
tutorials section, since I think it looks good and is not outdated.
I also added a simple step-by-step howto for getting started there.
Please review it, maybe it should be merged into the Git Configuration page.


More information about the kde-core-devel mailing list