On 3 déc. 2009, at 09:40, Laval Jannik wrote:
Yeh,
Now, I understand the process... (I am slow :) )
But, in this process we must specify versions and maintain it.
Is there a solution (in monticello maybe) to say a version of a
package is stable.
So in this case, we can say "I want last stable version of my
package" and we do not need to maintain ConfigurationOf.
The way to do it with Metacello: ConfigurationOfXXX project
latestVersion load
It takes the latest stable version, i.e. one which is not marked as
baseline, broken, or development.
Maybe this discussion is more global than moose community,
So I copy it in pharo mailing list.
Jannik
On Dec 3, 2009, at 13:15 , Tudor Girba wrote:
Hi Stef,
As I mentioned before, default represents the work in progress. It
can happen that the work in progress is the same as the previously
released version, and that is why you will see duplication.
Another possibility would be to reuse the previous configuration
and just mention the delta (of adding new packages), but I am not
sure this would scale in the long run.
So, the current process is:
- work on default
- when we release, we copy the method in a new baselineXXX
- we create a hardcoded version in versionXXX
Cheers,
Doru
--
www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Pharo-project mailing list
Pharo-project(a)lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Simon