website: AsyncAPI v3 related changes and website freeze
Reason/Context
In the last spec 3.0 meeting we discussed how we could slowly make changes to the website to fit it for v3 while still giving users access to v2 resources. We landed on the following suggestions:
- We create a temporary branch called
next_major_spec(this is what all other tools are using) to merge any related v3 changes into. Once we release v3, we merge that branch intomaster. - We will then deploy the latest commit before the merge on a sub-domain as frozen resources (never changes), where all the resources on v2 can be found, for example,
v2.asyncapi.com.
What do you think?
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 25 (25 by maintainers)
https://v2.asyncapi.com/ is here 🥳
just leaving a note for future. Let’s make sure this will not be needed, but might be that we will later on in the process rename
next-major-spectov2and persist it as a long living branchas opposite to initial assumption:
We will then deploy the latest commit before the merge on a sub-domain as frozen resources (never changes)I know we do not want to invest long term in old docs, but this repo is not only docs but also server configuration, redirects, and other stuff that we might need to adjust later
minimum is to add a
v2tag at least, that we can use to create a branch if neededwith
robot.txtwe can make surev2.asyncapi.comis not traversed and there can be a big banner on every page that it is old. Even certain navigation items can be removed, including content.Idea is that it is just one-time created old view of old docs. Just for reference
Minor comment: it should be
next-major-spec, to match the rest of the repos.And yeah as I said in the meeting I agree with that.