[Seaside-dev] versioning

[Johan Brichau]

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.

[1] https://code.google.com/p/seaside/wiki/Seaside311Changelog
[2] http://lists.squeakfoundation.org/pipermail/seaside/2014-February/030622.html

Johan

On 17 Mar 2014, at 11:01, Tobias Pape <Das.Linux at gmx.de> wrote:

> On 16.03.2014, at 17:59, Johan Brichau <johan at inceptive.be> wrote:
> 
>> Guys,
>> 
>> I would appreciate we do *not* change existing published versions in the ConfigurationOfSeaside3.
>> Version 3.1.0 was published as stable. It is bad practice to just upgrade a package version in there.
> 
> Yes. Please do not change a version that was released.
> That bit me hard a couple of times already.
> 
>> 
>> If you want to use 3.1.1, use that one. It has not been fixed yet.
>> But please do not break other people's workflow by sneaking in changes to published versions.
> 
> +1
> 
> Best
> 	-Tobias
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev