| Now do you think that what you call inheritance between versionSpec is
| a good way to share information.
|
| I though that I would define in version01 the repository and other
| common info and this is cool
|
| Now what happens is I want to change it I can override it in the
| following versionxx
|
| do you have a way to clone a new version without its father
| information?
I'm not quite clear on what you are asking, but I would think that it would be possible to generate a parent-less versionSpec method from it's parents ...
|
| It could be good when you we not want to load all the information and
| execute a lot of methods.
| I'm thinking about release pharo or moose with metacello and thinking
| that I would like to have a clean release version spec.
Okay, I would be even more inclined to possibly keep two parallel MetacelloProjects going ... one used by development with all of the gory partial versions etc., and the other that get's generated for releases that has only the 'public' milestones...
Am I in the ballpark of what you were thinking?
Dale