[Kde-scm-interest] Layout #2 of Git repositories for KDE

[Thiago Macieira]

Em Monday 05 November 2007 15:04:01 Johannes Sixt escreveu:
> > I guess we could merge playground with projects. New applications being
> > created are a "project" and they get moved directly into stable/kdereview
> > when they are considered stable. Thus we merge also the concepts of
> > stable and release-worthy.
>
> I understand; in particular, playground == projects makes sense. But I
> assume that stable/kdereview is meant as a placeholder for reasonably
> mature projects, not necessarily submodules of the KDE supermodule (or any
> other supermodule). It's a place to make the projects more visible and to
> point out the stable nature.
>
> (If projects in stable/kdereview were submodules of something, then moving
> them from kdereview to the final place inside stable/ would mean another
> awkward module move.)

Thankfully, we don't have to preserve history of the kdereview.git 
supermodule. It's there just as a "mamma, look how I'm big now!" (= please 
review this project).

If the target is a submodule of KDE, then the project will be imported with 
merge -s subtree (special case of copy-with-history) and the repository will 
be abandoned.

If the target is extragear, then all it takes is a mv in the server or pushing 
to the newly created repository.

In either case, we don't have problems with URL, since kdereview is meant a 
short-lived intermediary step. 2 to 4 weeks maximum.

Actually, come to think of it, none of the supermodules need to have a correct 
history, even KDE.git. Their only purpose in life is to allow easier checking 
out of the submodules, as well as to provide a top-level CMakeLists.txt that 
basically does:

	macro_add_optional_directory(*)

So that people like me can build a manageable 10 or 15 modules, instead of 150 
different applications and libraries.

On the releases/ tree, however, there's KDE.git as a supermodule again. But 
since this is releases, we have tags and special branches. The worst that can 
happen is kdetoys's case: the repository will continue to exist 
under /releases/KDE, but it won't be part of the KDE 4.x tags/branches. 
(The .gitmodules file will not reference it).

Which actually makes me think of a different idea. Posting in a new thread.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20071105/3ae42930/attachment.pgp