Le 8 déc. 2014 à 11:09, Tudor Girba a écrit :
Hi,
Indeed, I would want tool support.
The configuration does not depend on #stable. It currently depends on #development, but it should be changed to #stable. Could you handle that?
In Versionner, I assume that the development version is a baseline. If it not, I create a new baseline that becomes the new development version (understand, the current, not yet released version, I work on). Once Versionner has this baseline version, it resolves all kind of symbolic versions to the numbered versions for the release (but still keep the symbolic version in the baseline to use for dev version and next releases).
Also, actually we do not necessarily need a deep release. I extended Metacello with traversal and inspector support possibilities.
ok, so it should be easy. Versionners uses a command pattern so I assume you could call the ReleaseVersion Command on all the configurations without clicking on the Versionner UI. In this case, the only thing is to check that Versionner is happy with the current configuration.
Here is a snippet of code that you can try: | config project | config := ConfigurationOfVersionner. project := MTProject newFromVersion: config project development inConfiguration: config. (VSReleaseDevelopmentVersionCommand target: project devWorkflow for: nil) execute