But we need a working configuration for a Thales project so it has to work. Stef Le 25/6/15 20:59, Yuriy Tymchuk a écrit :
Hi Stef.
Yes, there is âjenkinsâ baseline, but after some time it stopped working. The problem is that JB cannot really maintain configuration of the projects developed by other people, because he is not aware what has changed and needs significantly more time than the dev that work with it.
Uko
On 25 Jun 2015, at 20:14, stepharo <stepharo@free.fr> wrote:
Yuriy
can you check with JB because he told me that he wrote a configuration for Wooden.
Stef
Le 12/6/15 13:48, Yuriy Tymchuk a écrit :Yuri
Just a quick side note:
my initial email was kind of a troll. Because when you ask for something about roassal and 3D, you get a reply about Roassal-Woden i.e. Roassal3D is not supported anymore, you have to use Woden instead. Now when you have to load Woden, you canât so you have to use the uber-long script on the Woden project page instead of conf. Thatâs why Iâve joked about using scripts instead of Metacello.
Uko
On 12 Jun 2015, at 12:25, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 12 Jun 2015, at 10:40, Stephan Eggermont <stephan@stack.nl> wrote:
On 12-06-15 10:24, Esteban Lorenzano wrote:
it was just an example of why using #stable in project dependences is a bad idea :) you made #releaseN.N to fix precisely my point. there should exist something like I say â3.*â #'release3' always refers to the latest stable 3.*.*.* I know :) Iâm just saying that I would like to have that as a standard mechanism, not a convention.
Esteban
Iâm sorry for being obvious here, I know this is known⦠problem is that Iâve seen far too much the use of metacello not for doing releases but to handle commits. I think it mostly has to do with the need to have exact reproducible builds (which is different from the need to have working software). That would be better handled with a (separate) SnapshotOf class i.m.o.
Stephan