On Nov 20, 2008, at 12:55 PM, Chris Chabot wrote:
So I think we either should break the correlation between the spec and
shindig release numbers (after all it implements the specs, but
isn't the
spec right? Just like firefox 3 implements http 1.1 :and there's no
correlation between the 2)), or we should change shindig's
development model
and think about how to sync spec versions with shindig internals /
experiments.
I'm certainly an outside observer, and not a committer, so take this
as you will, but I think I'd prefer that major architectural changes/
API breakage would be synced with new spec versions at least on some
level. This is a reference implementation of the spec, so some kind
of natural mapping from spec version to implementation version would
be ideal. Maybe, in the future, this would mean that you'd branch
sooner, before putting in pieces of the next upcoming spec version,
but that might not be necessary... the version should reflect the
latest spec that is *fully* implemented.
On the other hand, if you think that Shindig's architecture will
evolve more quickly than the spec, that's fair enough and in that case
it doesn't make sense to try to sync the version numbers.
Cheers,
--
Tim Moore
Atlassian Plugin Developer
