yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #14479
Re: Migrating to GitLab
-
To:
yade-dev@xxxxxxxxxxxxxxxxxxx
-
From:
Janek Kozicki <janek_listy@xxxxx>
-
Date:
Mon, 7 Jan 2019 17:39:28 +0100
-
Face:
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUBAQEtLS1KSkpRUVFXV1dYWFhjY2Nzc3N3d3eHh4eKioqdnZ24uLjLy8vc3NxVIagyAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH2AIVEzgS1fgQtQAAAjRJREFUOMtt1DFv00AUAOAzFQNbjigSyoQaRaBMhKgLUyKXpVNNeUpk9vyDqFJhQ1kiBuaqAwJCqvPtSLY7RlTn5+5IdnYkkt/AOyfxXVLe5vf53Z1875kd34tOEax8djmj6GyjhB5bxz50GdsVZr9fqRjZwAtKOJw5Wqs2MMZ16ALHsaDncF7xAHix1oEFHAB8f+pRjcO4gfZDykcYzbiucRolOLUJ6kjA0xtVt+A6TySlM0RajIpK6DzwKZ/nOYbF/gclHMo1ZOHYY/+Ha+AWuM+3oMS4eeqYzZ8FiCltgUqI8cd2wwAVpJk+8LWYjBtnJdQpHQqJMd4Oxt4bU9ESiFGc5hkqaH74asAX4iabP5I5gZ+qjgGlJCqZa3h3lxhoeVcSE1qLQC4sqKOK9MGW9E3izFqqHokoztLFEgXg31sbZEKnWi2T74A4NxfVQqlkjKtcAWD+zcArFEES01dR0E/nnV0IgugmDd/2L84sOAouRBBHEc7gtc8teDkRlE0iNQPo2w3Xhh/D4TCIQ4LRLoTvgwjj6RRgavdurxYGMaIuGOyAW/PpNlCcU9/93AHenAWYjPoAwa+G3e3to/MgFNTAEKvKDjzuCzHTnY3qqdXtx24VijzQfZ0yewZ5cwRFQaa+mIYr1uI0I76+3W4xhlvoVRwOA0Fdl64HlJnxP6T8YpX/Lga4Wv4A3ErrU5oTfN7Mu/llXMl8RXEPji/lQkN3H7qXqgC2By47EXeU/7PJ/wPxRKMnuZwIeAAAAABJRU5ErkJggg==
-
In-reply-to:
<3829b8a1-cf97-83da-a8b8-e7e9ba303ee5@grenoble-inp.fr>
Bruno Chareyre said: (by the date of Mon, 7 Jan 2019 16:59:53 +0100)
> Daily builds would be based on the develop branch.
good, that answer my question from other mail.
> > (by the way, with a tighter control on development, would we still
> > need a distinction between "yade" and "yadedaily" packages ?..)
>
> Yade is stable release, not updated very often, included in main
> debian/ubuntu repos.
> Yadedaily is updated more than daily, after each change to the source
> code, not included in debian/ubuntu repos.
> They are very different things and I think we need both.
agreed.
> > Also, with "develop" and "master", I guess any proposal for code
> > modification would have to be closely examined and validated twice :
> > - once to make it into "develop"
> > - and once, to make it from "develop" into "master"
> > ?...
> There is no reason to check the develop->master merge if everything in
> develop is already validated by regtests + human review.
> Our github/master corresponds to "develop" more or less.
> Merging develop into master in the new model would correspond to Anton
> calling for update and releasing 2018.b. More or less.
agred.
> We probably need a liberal, truly unstable repo on the top of this, at
> least in a transitory phase, so that everyone can play with gitlab a bit
> and break everything with no limit. For instance to compare --no-ff,
> --only-ff, and other variants.
how about calling it experimental ? :-))
And yes, we definitely need something like that.
Where git reset --hard is nothing to be afraid of.
--
Janek Kozicki
Follow ups
References