Issue #253: implement suggested fix ... let's see what blows up
Issue #253: slash lineup to just 3.2.0 ... to see impact of change
Issue #253: by implementing #canUpgradeTo: logic for baselines, I'm able to preserve Issue #181 semantics (allow upgrade when same github repo except for projectVersion) while recognizing lock when applied ... let's see if tests confirm this:)
tracing to understand travis-only errors
tracing why MCB tests loaded with TravisCI_1 and TravisCI_2
need to pass the exception
split out Metacello-GemStone-TestsMCB so that Metacello-TestsMCB doesn't get loaded with both TravisCI_1 and TravisCI_3 (for GemStone)
Issue #247: another stab at clean up ... found some inconsistencies that might be related
more tracing for travis-only errors
a whole lotta tracing ...
Issue #253: final fix to bug? fortunately I've got enough tests that I am "forced" into a proper fix:)
Issue #253: remove tracing ... tweak test ... BTW, MetacelloProjectRegistration>>canUpgradeTo: was semantically changed in f503567 "a while lotta tracing" and was decisive in getting the failing tests to pass
re-enable the full lineup
tracing and reduced lineup to debug non-gemstone issues
fix tracing
Issue #253: fix up MetacelloScriptingSuccessTestCase>>testIssue136Loading
remove some futile tracing:)
in copyForRegistration:onWrite:, the arg must be valid ... otherwise trouble may ensue
bullet proof MetacelloProjectRegistration>>currentBranchName and fix cleanup for MetacelloBasicScriptingTestCase>>tearDownPackageList
symmetry for validation