On 16-06-15 14:28, Thierry Goubier wrote:
Does that mean that we could characterize NeoJSON #stable as being at
version 1.0.X, and the only possible evolutions are 1.0.Y versions
(unless we see a major extension of the JSON format ...) ?
(In which case #stable on NeoJSON would be equivalent to '1.0.[*?]'
for Metacello)
((I don't remember the special character for Metacello versions: *, ?,
&?))
Yes, when using the naming scheme of Seaside, Magritte and Grease, it
would be
#'release1'
and as long as there is no need for #'release1.1' or #'release2' the
#stable will
work. There will be new versions connected to that whenever something
deep in Pharo
gets fixed/changed. If that change is not backwards compatible, the
platform attribute
might be used to select a different version for the newest Pharo.
Stephan