30 Jun
2014
30 Jun
'14
11:52 a.m.
Yes, I saw this. But, I did not see what happens when you have nested
configurations. How do you control which version of the nested config to
point to in your new version?
Cheers,
Doru
On Mon, Jun 30, 2014 at 11:27 AM, stepharo <stepharo(a)free.fr> wrote:
It is two clicks.
Christophe did a video you should check it in the Pharo mailing
In a nutshell
in devlopment you commit normally your packages.
- to load you click on development and load the latest ones.
in dev if you change the baseline, (you change it)
- you click on dev
- save (to development) + commit
to release
you click on development
- release (-> this creates a new version)
- commit
:)
done
--
www.tudorgirba.com
"Every thing has its own flow"
Uko
On 30 Jun 2014, at 10:32, stepharo <stepharo(a)free.fr> wrote:
Hi
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I really think that
- everybody should use versionner :) because now that I use it it is
really nice.
- we should use baseline for development during development
- we should use stable or versionned for external packages such as
XML.
- with versionner we can release at the end of every week or two in
probably some clicks.
(I can ask christophe for some improvements).
So can we agree on that because we can make sure that we have the
advantges that now
and have at the end of every week a versionned released?
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev