1.2 has been released prematurely and 1.1 docs are missing

[mattheworiordan]

See #843 (comment)

This has been merged into the website now and released too, making this more of an issue which needs to be fixed with high priority.

The 1.2 work should remain on a feature branch until launched.

[QuintinWillison]

I believe I've fixed this with reverts 280a99b and e308caf, in that 1.2 is now back in an integration branch.

I don't believe there's any more work I need to do on this issue, and I've responded to @mattheworiordan elsewhere regarding versions folders.

[mattheworiordan]

@QuintinWillison Can you please be specific regarding your statement "we've effectively skipped a version now in the docs".

I had stated why in #843 (comment)

"This is important because if someone is now using 1.1, what docs do they refer to? The process we followed before was to simply copy the files into a 1.1 versions folder, and voila, you magically have 1.1."

Only creating a 1.1 version because it's changed is wrong for a few reasons:

• Anyone on a 1.1 SDK now has no way of viewing 1.1 docs. Would they view 1.2 or 1.0? How would (or should) they know. We should just show them 1.1 docs.
• Any changes you make subsequently to 1.2 docs, which may not apply to 1.1 in future (yes, not you, but someone else may do this) will inadvertently now create a change that is potentially incompatible with 1.1
• We have no single view of what the SDK docs look like at 1.1
• Users will have a pretty broken experience if they view push docs with version 1.1, then jump to the realtime docs, and suddenly see 1.2. Every time they jump between docs they may get a version that doesn't match the SDK they are using.

So reopening this issue as this is not resolved.

[QuintinWillison]

Thanks. I'll have a go and see what that looks like.

[mattheworiordan]

@MarkWoulfeAbly can this be closed?