An abstraction that is a little more ‘semantic versioning’ than #stable.
If your project depends on Seaside 3.0.x, you don’t want it to depend on Seaside 3.1.x when that becomes the new #stable.
But you also don’t want to depend on a specific bugfix version (e.g. 3.0.9).
The solution is a symbolic version #release3.0 that will point to the latest bugfix version in the major 3.0 version.
We’ve started adopting this a couple of years ago for Grease and Seaside and it pays off.
cheers
Johan
> On 06 Apr 2015, at 02:59, Sean P. DeNigris <
[hidden email]> wrote:
>
> What is the purpose of the following method:
> release33: spec
> <symbolicVersion: #'release3.3'>
> spec for: #'common' version: '3.3.0'
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context:
http://forum.world.st/releaseXyz-Symbolic-Versions-tp4817748.html> Sent from the Metacello mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Metacello" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
> For more options, visit
https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/d/optout.
Locked
