Ok I will update the stable setting because it was just loading the development version so breaking the point of stable
Igor such information should not be only in your head!!!!

 
it is work to do..
but i am not sure it is worth doing. Pharo 2.0 officially not supported by Athens, so why we should worry about staying compatible?
Yes, in perfect case , configuration baseline should contain branch to load different versions for 2.0 image, and for 3.0.

But to do that , first i need to learn (again) how to do it :)
We certainly need a UI tool for configurations, because keeping all those "how to-s" in head
becomes tedious and counterproductive task.

yes and it is coming, versioner will help us for that. 
But to me it looks like you did not write enough configurations. I hate writing them but I do not it because there is no other ways to 
manage quality and reproducibility. If this is the price to pay, I pay it because this is what I want. a ONE CLICK loading system.
I take a reference one and I copy. So now this is done.

Have a look and see if it loads what you think it should. 

Stef