Re: [w3c/manifest] Specify how updates work (#446)

I'm strongly in favour of a versioning scheme to enable predictable updates.  As we all know, versioning is a solution to this problem which is used and well-understood across the whole industry, and it should be easy to retain backwards compatibility.

I would suggest using semver unless there are compelling alternatives or reasons not to (which seem unlikely to me at this point).  Semver is a very well-trodden path and avoids reinventing wheels.  I don't think it's compelling to say that semver leads to a lot of complexity, because it's essentially a very simple concept which is already well understood by many developers and already has multiple implementations.

In other words, update mechanisms via versioning is already a solved problem, so I think it makes sense to treat it as one rather than looking for a new solution.  Reinventing wheels would mean a whole new updates and/or versioning scheme for developers to learn, even though it would only exist in this one place.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/446#issuecomment-904486884