On May 23, 2013, at 10:17 AM, roberto.minelli@usi.ch wrote:
+1000 Camillo!! I'd really appreciate a "better" MC configuration mechanism!
us too. Now we have to deal with the fact that latest version of metacello could not work in Pharo anymore Stef
On May 22, 2013, at 5:53 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
I recently spent some time to revise how to write Metacello Configurations.
Observation: ============ - many configurations are quite a mess - many configurations duplicate code internally - many configurations have archived development versions
For Pharo 3.0 I made a new Configuration template which improves and documents these observed points in quite some detail. Simply load a new 3.0 image and create a new configuration from the monticello working copy browser.
Solution: ========= - specify external projects in separate, reusable methods - only have ONE development version you regularly update - do not use version numbers for the development version - only make a version number when you release something stable AKA not #development - name the baseline after the first version that introduces it
What do you think?