A few quick things about the config:
* while you're working on the spec version, please integrate my config so we
can play with it without loading the full Glamour :) It only changes the 1.0
baseline, so it should not effect your current work (and remove Glamour from
the load instructions since it's loaded automatically now)
Yes, I used your configuration that you sent me. Now you can use the following instructions to load Versionner without loading the full Glamour.
-=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=-
Gofer new
� �package: 'ConfigurationOfVersionner';
� �load.
(Smalltalk at: #ConfigurationOfVersionner) perform: #loadWithGlamour
-=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=--=-=-=-=-
* I noticed you are creating version 1.20, 1.21, etc., all with little fixes
and "blessing: #'development'". After many conversations with Dale, I now
understand that the point of marking a version #'development' is so you can
change it without making new version numbers.
Yes, I am fixing some bugs in Versionner.�I will take into account your recommendation
�
* the default for Metacello is to load all packages, so the last line of
your baselines (spec group: 'default' with: #(...).) is unnecessary and
creates the burden of having to be manually updated if your project
structure changes
I didn't know that, you're right . I removed it. Thank you :)