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

List:       kde-edu-devel
Subject:    [kde-edu]: Re: [Kde-scm-interest] Re:  kde-edu is now on git
From:       Ian Monroe <ian () monroe ! nu>
Date:       2011-04-04 19:43:56
Message-ID: BANLkTi=hhJfuhWHSH6pnRMWMNnXUfs8__w () mail ! gmail ! com
[Download RAW message or body]

On Mon, Apr 4, 2011 at 14:34, Sebastian Stein <seb_stein@gmx.de> wrote:
> 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?

If only there was some sort of meeting where the kdeedu developers
could get together and decide such things... :D

Seriously though one advantage of having repos like 'kbruch' is that
you really only need to coordinate with other kbruch developers. So
the problems being addressed by various 'git workflows' are mostly
moot since I'm guessing most kdeedu apps have only one or two or three
developers who can communicate with each other quite easily. Its quite
a different situation then kdelibs and kde-workspace etc.

Ian
_______________________________________________
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]