<br clear="all">M. Farzad Sehat<br><a href="mailto:farzad.sehat@gmail.com">farzad.sehat@gmail.com</a><br>
<br><br><div class="gmail_quote">2009/11/13 Xavier Oswald <span dir="ltr"><<a href="mailto:xoswald@gmail.com">xoswald@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 12:48 Fri 13 Nov , Mildred Ki'Lya wrote:<br>
> You can always create repositories under your own homedir in alioth.<br>
> <a href="http://wiki.debian.org/Alioth/Git#UsingpersonalGitrepositories" target="_blank">http://wiki.debian.org/Alioth/Git#UsingpersonalGitrepositories</a><br>
<br>
</div>Right, I forgot this fact.<br>
<div class="im"><br>
><br>
> The questions are:<br>
><br>
> • What happens to the stable branch?<br>
> • Where will Benoit commit? I don't think he should commit in the default<br>
> branch (whatever it is called, for the moment it is called stable).<br>
> Sometimes he breaks the bootstrapping and we want to always have a version<br>
> of the compiler that can bootstrap and do useful things.<br>
><br>
> Now, this was how I saw the repository:<br>
><br>
> • master: where Benoit commits. He (supposedly) merges with stable frequently<br>
> • stable: where there is a compiler that always bootstrap (or if it doesn't,<br>
> that is very rare, we all make mistakes).<br>
> • lisaac-VER: where the version VER is prepared, it always bootstrap and only<br>
> minor changes (bugfixes mostly, and accepted features for this release) are<br>
> allowed in. This would be a more restrictive subset of 'stable'.<br>
<br>
</div>To make it simple:<br>
<br>
Benoit commit to master for his development and take feature from other<br>
branch name_feature and merge to master. After having sometimes a stable master<br>
branch he merge with stable.<br>
<br>
So only Benoit will commit to stable and master.<br>
<br>
stable will be used for new releases and tagging will be done from this branch<br>
<br>
For lare new feature averybody is allow to create a branch name_feature for<br>
doing new development.<br>
<br>
All lisaac-X branch will be deleted.<br>
We will tag all lisaac-X new release.<br>
<br>
Having lisaac-X branch and lisaac-X tags make confusing about where is what.<br>
<br>
This will made our development process clear and simple.<br>
<br>
<br>
And don't forget that you can development a new branch on your machine and tell<br>
Benoit/the list, that we can fetch a new branch somewhere on a machine.<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br>This is exactly the new policy, great explanation :<br>Please do not commit stable, master, create your name_feature branch follow the new rules and have fun.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5">
<br>
Greetings,<br>
--<br>
,''`.| ====== Xavier Oswald ====== | mail: <a href="mailto:xoswald@debian.org">xoswald@debian.org</a> |<br>
: :' :| Engineer at CALDERA GRAPHICS | <a href="http://www.caldera.eu" target="_blank">http://www.caldera.eu</a> |<br>
`. `' | GNU/LINUX Debian Developer | <a href="http://debian.org" target="_blank">http://debian.org</a> |<br>
`- | Isaac Project Developer | <a href="http://isaacproject.u-strasbg.fr" target="_blank">http://isaacproject.u-strasbg.fr</a> |<br>
</div></div><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
iEYEARECAAYFAkr9TpAACgkQpDDGqoi7tR5bewCgnbkmsvu76b96eX0wOI64r4v6<br>
AqoAniUQ9yj5wL+4wqjWXbyDgjDpfZ2s<br>
=ryQD<br>
-----END PGP SIGNATURE-----<br>
<br>_______________________________________________<br>
Lisaac-devel mailing list<br>
<a href="mailto:Lisaac-devel@lists.alioth.debian.org">Lisaac-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel</a><br>
<br></blockquote></div><br>