New Git Repositories Organization

[Farzad Sehat]

M. Farzad Sehat
farzad.sehat at gmail.com


2009/11/13 Mildred Ki'Lya <ml.mildred593 at gmail.com>

>  On 11/13/2009 06:44 AM, Farzad Sehat wrote:
>
> Below you can find the new organization of he Lisaac git repositories. You
> must notice that any source code is deleted, this is just
> a new organization.
>
> Lisaac team has now a new git organization policy:
>
>    - Nobody must commit to the master branch of the compiler.git
>    - Any commit in the master branch of the compiler.git is prohibited and
>    after 3 warnings you are baned from the team
>    - Nobody must create Git *repository* without asking first to Xavier
>    Oswald <x.oswald at lisaac.org>
>
>  You can always create repositories under your own homedir in alioth.
> http://wiki.debian.org/Alioth/Git#UsingpersonalGitrepositories
>
>
>    - You can create *branches *in each Git repositories with the following
>    rule:
>
> <name>_<feature> where feature is the reason why you want a new branch
>
>    - Please make the necessary to remove all old branches and to follow
>    the new policy
>    - Please update your code with the new beta compiler release in order
>    to be ready for the future stable release
>
>
> The questions are:
>
>    - What happens to the stable branch?
>    - Where will Benoit commit? I don't think he should commit in the
>    default branch (whatever it is called, for the moment it is called stable).
>    Sometimes he breaks the bootstrapping and we want to always have a version
>    of the compiler that can bootstrap and do useful things.
>
> Now, this was how I saw the repository:
>
>    - master: where Benoit commits. He (supposedly) merges with stable
>    frequently
>
> That's the new policy, Benoit commits in the master and merges not only
from stable but from all name_feature
where he takes what he thinks is interessant.
Stable branch is the stable branch. It must be stable a compiler which
bootdtrap and is stable.
In the new policy there is not lisaac-VER branch, only master stable and
name_feature. This policy require that
a new branch is created only if it is realy necessary. If you think you have
something to improve the compiler
you create a branche name_feature where feature is the improvement, bugs
fixes ...


>    -
>    - stable: where there is a compiler that always bootstrap (or if it
>    doesn't, that is very rare, we all make mistakes).
>    - lisaac-VER: where the version VER is prepared, it always bootstrap
>    and only minor changes (bugfixes mostly, and accepted features for this
>    release) are allowed in. This would be a more restrictive subset of
>    'stable'.
>
> Mildred
>
> --
> Mildred Ki'Lya
> ╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
> │ Jabber, GoogleTalk: <mildred at jabber.fr> <mildred at jabber.fr>
> │ Website: <http://ki.lya.online.fr> <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
> │ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
>
>
> _______________________________________________
> Lisaac-devel mailing list
> Lisaac-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20091113/91a5ff71/attachment-0001.htm>