[Kde-scm-interest] Layout of the Git repositories for KDE (proposal #2)

[Johannes Sixt]

Thiago Macieira schrieb:
> Em Monday 05 November 2007 16:42:37 Johannes Sixt escreveu:
>> Thiago Macieira schrieb:
> Yes, releases/KDE.git still exists. The releases/ tree is unchanged from the 
> previous proposal.
> 
> And releases/KDE.git is not the same repository as meta/KDE.git (or 
> stable/KDE.git in the old proposal). Note the existence of kde-l10n.git 
> inside it, for instance. The releases repository is just for the tagging.
> 
>> But then you also needed stable/KDE.git. Think of a cross-module change:
>>
>> * I change some API in kdelibs.
>> * Then I need to update kdebase, etc.
>> * In order to make the change atomic, I must make a commit in KDE.git that
>> includes *my* new states of kdelibs, kdebase, etc.
>> * I must make this commit available to others, else they see
>> inconsistencies. 
>> * Where do I do that? stable/KDE.git is the only 
>> reasonable place.
> 
> Yep, but this is meta/KDE.git in this proposal. I.e., all developers must have 
> push access to all the meta repositories.

Now I am confused. How is meta/KDE.git different from stable/KDE.git?

Let's see if I can figure it out:

- meta/KDE.git is a one-shot repo that consist only of gitlinks to the 
submodules. It is a convenience for developers who want to checkout more 
than one submodule.

- stable/KDE.git is the clone of release/KDE.git on the way to the next release.

Right?

-- Hannes