Re: [Pharo-project] Think about migration upfront! (was Re: squeaksource is down - a different perspective)

2011-05-02 Thread Miguel Cobá
Sometimes it is just enough to let the old versions in the old system and start afresh in the new system with the last version of the project. I think that the main reason for a project not being accepted is that they lack enough traction and aren't end-user appealing. Also, there can be a few ha

Re: [Pharo-project] Think about migration upfront! (was Re: squeaksource is down - a different perspective)

2011-05-02 Thread Tobias Pape
Am 2011-05-02 um 10:00 schrieb Janko Mivšek: > I think we should learn very carefully from Gemstone migration > experiences to develop our Smalltalk systems *upfront* with migration in > mind. > > Just see all recent (or less recent) examples: MC2 seems too radical to > be easily migrated from M

[Pharo-project] Think about migration upfront! (was Re: squeaksource is down - a different perspective)

2011-05-02 Thread Janko Mivšek
I think we should learn very carefully from Gemstone migration experiences to develop our Smalltalk systems *upfront* with migration in mind. Just see all recent (or less recent) examples: MC2 seems too radical to be easily migrated from MC1 and obviously designed without migration in mind, Squeak