On Fri, Jun 12, 2015 at 1:48 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:

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.

As a sidenote (and since Yuriy mentioned Roassal), we would like to address the versioning (and release management) of roassal at ESUG (Camp Roassal) since Roassal was being developed really fast and it was hard to keep up.

Semver is good for not breaking things (if applied properly), but I feel it hides a little bit the extent of change... a project could go from version 1 to 10 with several very little bc-breaks and then from 10 to 11 there would be complete redesign... and you can't tell the difference just looking at the number, which is bad for updating (

As for #stable, etc., they are very useful for tools which I only use as a user... e.g. PharoLauncher or QualityAssistant

my 2��

Peter