I had to think about this for a while. Let me see if I can summarize where we are: - I wanted to translate the pre-BaselineOf workflow of "specify loose dependencies generally (e.g. #stable) in the #baselineXyz: method, and precisely in the #versionAbc: method" to "specify loose dependencies generally in the BaselineOf, and precisely in the ConfigurationOf" - You're saying that I can't (or shouldn't?) do that, but should instead specify them generally in the dev branch, and pin them down each time I release, so I would: 1. Commit dev with the specific versions 2. Merge into master 3. Commit dev again with the general project versions to continue my work
Does that all sound accurate? Two things to note that I'm not sure were clear: - I have no control over the other projects and assume they do not use the #releaseXyz discipline - I do not generally use issue branches for projects that I work on alone because IMHO it adds much complexity to the workflow Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/BaselineOf-s-and-Loose-Dependencies-tp4885749p4887415.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
