Versioned spec docs about spec HOT 5 CLOSED

I believe this question was settled in https://github.com/buildpacks/rfcs/blob/master/text/0027-spec-api-branches.md

from spec.

Could we use tags on the repo instead? I know that is a bit odd because a #platform-0.2 would also point to an arbitrary version of the buildpack api, but it might be a little easier to read for the 80% who just care about the latest.

from spec.

The main drawback of using tags are:

1. It doesn't allow for us to go back and fill in any missing information, express further understanding, or even just fix typos. (without using "mutable tags" which are a big no-no in git).
2. We have multiple unsynced versions for different components. We would need to create multiple tags per component which I would say would be harder to comprehend than looking at a list of all versions in a repo.

IMO, it would be very apparent what latest is simply by increment of the version.

I can make this an RFC if we'd like to have a long form discussion around it.

from spec.

Yea, let's RFC this one. I think at a minimum we'd want to dump the older versions in a subdir so that most people don't have to think about it.

from spec.

I agree on an RFC, and I'm also of the opinion that we should be using Git tags for this. Branching might also be appropriate for evolution of the spec at a given version, but even that makes me very queasy.

from spec.