One thing that I like about the split (image, changes, sources) approach is that the changes seldom go bad, providing a lot of protection against lost work. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Marcus Denker Sent: Sunday, November 29, 2009 3:26 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Method versioning in Pharo images On Nov 29, 2009, at 1:27 AM, csrabak@bol.com.br wrote:
What I would want to have is a server with all old code that than is queried by the image...
Marcus, let me ask to put in this wish list we could have then a versioning system similar to RCS/CVS and family where you name (in fact you number and give then alias names, but I digress. . .) the versions and can put comments documenting the code changes for the non obvious things in code.
Yes... we do have MC, but those compressed .zip snapshots are not really good as a history model to query (the information is there, but you need to anpack all zips...) One important thing that needs to be done is to move on from having multiple mechanism in parallel (sources + changes, MC) to one.
An escape hatch for the .changes limit would be to serialize all the versioning information in a .versions file.
yes, but it would be very large. Marcus _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project