[ANN] Screencast on Versionner

Hi, 

On 30/04/15 13:50, Esteban Lorenzano wrote:
> I made a small video on how to use Versionner.
> Versionner allows you to manage project configurations in a smooth way.

Nice, good to see how versionner is supposed to be used

Stephan

Thanks esteban
I would not promote groups because we want to get rid of them.

Hi, 

I made a small video on how to use Versionner. 

Versionner allows you to manage project configurations in a smooth way. 

https://youtu.be/cFRJDuWL-Q0

I know… is not “Kilon’s quality”… but I hope it will help :)

cheers, 

Esteban

Esteban

why you did not define the dependencies between the packages?

Stef

Hi, 

I made a small video on how to use Versionner. 

Versionner allows you to manage project configurations in a smooth way. 

https://youtu.be/cFRJDuWL-Q0

I know… is not “Kilon’s quality”… but I hope it will help :)

cheers, 

Esteban

mostly because I wanted to keep the screencast short an easy. 

Then we can remove the groups part :)
BTW we should register (put a link and store the videos) these videos somewhere and not let them on youtube.
I want to be able to use them for the Mooc
Stef

mostly because I wanted to keep the screencast short an easy. 

advanced configurations might need package dependencies, but other times you do not need them. 

Esteban

On 30 Apr 2015, at 16:03, stepharo <[hidden email]> wrote:

Esteban

why you did not define the dependencies between the packages?

Stef

Le 30/4/15 13:50, Esteban Lorenzano a écrit :

Hi, 

I made a small video on how to use Versionner. 

Versionner allows you to manage project configurations in a smooth way. 

https://youtu.be/cFRJDuWL-Q0

I know… is not “Kilon’s quality”… but I hope it will help :)

cheers, 

Esteban

On 30/04/15 16:02, stepharo wrote:
> I would not promote groups because we want to get rid of them.

No we don't. We need first class support for them
in the tools. We cannot map variants decently without
lots of duplication otherwise. It is a 5 dimensional
problem that is not going to get easy.

Stephan

On 30/04/15 16:06, Esteban Lorenzano wrote:
> mostly because I wanted to keep the screencast short an easy.
> advanced configurations might need package dependencies, but other times
> you do not need them.

Well, it either is 1st steps in configurations, and then
you can keep them out, or it is about configuration
management, and then we want to see the required
complexity. That can be in several videos, solving
the different problems different users might run
into.

Stephan

Le 30/4/15 18:06, Sergio Fedi a écrit :
> Excellent work Esteban!
>
> ​Question for the list:
>
> What are groups?
>
> What do they model?
>
> What problem do they solve? (or why are they useful)

Think about them as other configurations.
Because they are not much less than that.
Avoid them as much as possible.

Stef

On 30/04/15 18:06, Sergio Fedi wrote:
> Excellent work Esteban!
>
> ​Question for the list:
>
> What are groups?
>
> What do they model?
>
> What problem do they solve? (or why are they useful)

When managing configurations, choosing the right
granularity is critical to reducing the amount of
work needed. Groups allow one configuration to
be used to manage multiple combinations of packages.
With groups it becomes easier to manage variants.
Seaside can be used with any combination of
adapters, rest, jQuery, Scriptaculous, Bootstrap etc.

The simplest example was shown by Esteban in the
screencast: in a production environment one might want to
not load the test packages, so one has groups
core, test and default (=core+test).

Our tools currently do not support groups well
enough, as we don't register which groups are
loaded in the system.

Stephan

Sergio,

When you configure the Test package you add the Core as its dependency.

eg:
spec package: 'Core-Tests' with: [ spec requires: 'Core ].


Regards!

Esteban A. Maringolo


2015-04-30 16:06 GMT-03:00 Sergio Fedi <[hidden email]>: