stepharo wrote > there is a huge time / energy investment problems. I don't see it. The simplest thing (which is 0 extra work AFAICT) would be to tag the last version before we start updating for 5.0 as something like 'Pharo-4-final'. Almost as easy would be to have a branch per version, so e.g. typos could be merged back if someone was interested. But maybe I'm missing something - where specifically do you see the time & energy investment? Because I think we could've set it up in less time than it took me to write this reply!
----- Cheers, Sean -- View this message in context: http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514p4817525.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
