> On 08 Jun 2015, at 18:22, Alexandre Bergel <alexandre.ber...@me.com> wrote: > >> Well at least for me it is certainly not clear what release policy is >> Roassal following; i.e. if I see a minor version change what to expect, if >> any BC breaks were introduced, etc. Of course this is extra effort for the >> person doing it, so it should be taken with care. But there are certainly >> things to be discussed about this. > > Hi Peter, > > Indeed, we have not been good at producing a descent version numbering > schema. > My position was always this one: the last version should always fit your > need. However, some product favored stability when Roassal is used in a > commercial setting. > We will be more careful when updating the configuration with a proper version > number.
Versioning is in fact a complex thing. That’s why I suggest to have a brainstorming session during the camp. Uko > > Cheers, > Alexandre > > >> >> On Fri, Jun 5, 2015 at 7:31 PM, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote: >> Oh, then it’s my bad. Last time I’ve checked it seemed that it wasn’t >> updated for a long time. Maybe I was wrong. >> >> Uko >> >> >> >>> On 05 Jun 2015, at 18:08, Peter Uhnák <i.uh...@gmail.com> wrote: >>> >>> There sure are, look at ConfigurationOfRoassal2>>version*: >>> >>> and in my baseline I have something like >>> >>> ~~~~~~~~~~~ >>> spec >>> project: 'Roassal2' with: [ >>> spec >>> className: #ConfigurationOfRoassal2; >>> versionString: '1.52'; >>> repository: >>> 'http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/' ]; >>> ~~~~~~~~~~~ >>> >>> Peter >>> >>> On Fri, Jun 5, 2015 at 4:37 PM, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote: >>> But are there numbered version to refer to? >>> >>> Uko >>> >>>> On 05 Jun 2015, at 16:34, Peter Uhnák <i.uh...@gmail.com> wrote: >>>> >>>> >>>> >>>> On Fri, Jun 5, 2015 at 3:29 PM, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote: >>>> I’m interested in participating. Personally I’d like to talk more about >>>> design decisions behind roassal ecosystem, release strategy and so on. >>>> Usually when I work with Roassal I have this issue that things are >>>> breaking because of rapid changes, or because of the differences between >>>> different parts of roassal. Maybe someone is also concerned about this, so >>>> we can discuss and maybe improve something… >>>> >>>> Yes I am also interested in this, right now I am actually using quite old >>>> version (month+) because I didn't have time to keep up. :) (Arguably 90% >>>> of my problems were from infamous composite shapes. :)) >>>> >>>> Peter >>>> >>>> Uko >>>> >>>>> On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.ber...@me.com> >>>>> wrote: >>>>> >>>>> Dear Colleagues and Friends, >>>>> >>>>> We are happy to announce we will organize a CampSmalltalk about the >>>>> Roassal visualization engine, on _Sunday 12 July_. >>>>> >>>>> As far as we have seen, the interests are multiple. Here is a list of >>>>> topics we will happy to work on: >>>>> - Port of Roassal on VisualWorks >>>>> - Using Roassal on Gemstone >>>>> - HTML/JavaScript export >>>>> - Improving Grapher, our charting library >>>>> >>>>> If you wish to participate, get in touch with us. Since we will probably >>>>> have a sponsoring of the event, it would be nice to know how many will >>>>> attend to ease the logistic and the pizza ordering :-) >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >
