Is there any way to lock down a version in Metacello so this can't happen? This would seem to be a critical capability of a version control system.

John

John O'Keefe [|], CTO/Principal Smalltalk Architect, Instantiations Inc.
Skype: john_okeefe2     Mobile:  +1 919 417-3181 (Business hours USA Eastern Time zone (GMT -5))
john_okeefe@instantiations.com
http://www.instantiations.com
VA Smalltalk...Onward and Upward!


On Tue, Mar 18, 2014 at 9:26 AM, Philippe Marschall <philippe.marschall@gmail.com> wrote:
On Mon, Mar 17, 2014 at 5:48 PM, Johan Brichau <johan@inceptive.be> wrote:
> In any case, I also want to suggest to release version 3.1.1 by the end of the month.
>
> There are a good number of bugfixes and improvements [1], the jQuery binding got upgraded and the Gemstone port has just a few dangling items I can probably fix by then.
>
> Philippe, I think it would be good to also have the 'change' to JSON canvas in there [2]. What do you think?
> I have been writing a number of integrations that use the new JSON canvas and I think the 'new' behaviour is definitely more appropriate. I also believe it's backwards compatible but I will check and let you know.

Sounds like a plan.

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
seaside-dev@lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev