[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu-devel
Subject:    [kde-edu]: Re: kde-edu is now on git
From:       Sebastian Stein <seb_stein () gmx ! de>
Date:       2011-04-04 19:34:11
Message-ID: 20110404193411.GA4049 () hpfsc ! de
[Download RAW message or body]

Ian Monroe <ian@monroe.nu> [110404 19:50]:
> Enjoy. :)
> 
> The 4.6 branch and master will now be developed in Git. SVN is locked
> read-only.

That is really great news!

But now starts the trouble: How do we work with git? I have seen that there
was a meeting about it, but as far as I can tell, there is no final outcome
or even agreed workflow.

I cloned kbruch, but now I wonder how to move forward? Is it expected that
all feature development happens directly in master or shall we create
branches? And if we use branches, are there any naming conventions?

Is this document

http://community.kde.org/20110213_GitWorkflowAgenda/StevesIdea

the one to follow at the current point?


Thanks in advance,

Sebastian
_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu
[prev in list] [next in list] [prev in thread] [next in thread]