Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a basic landing page to which we can link from our outbound … #30988

Merged
merged 4 commits into from
Apr 23, 2021

Conversation

pragmaticpat
Copy link
Contributor

…emails re: v2 support

@meganesu - I'd appreciate you weighing in on the content here. Thanks!

This is not a blog post

Description

Implementing a basic landing page for plans related to supporting Gatsby v2 as we continue to pursue and invest in the future of Gatsby v3+.

Documentation

I don't think this section applies

Related Issues

No related issues

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Apr 21, 2021
Copy link
Contributor

@meganesu meganesu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments! Overall, this is in good shape.

One thing that I think is missing is setting expectations for how we want users to engage with us if they run into problems (with v2.32 or with v3). Mainly to clarify how we want them to reach out (open an issue, email support) and what kind of support they can expect from us. I'm assuming there would be different expectations for active vs. maintenance support.

I'm not sure if you've opened a PR in mansion yet, but you'll also need to add this file to the docs sidebar to get it to display in the hierarchy.

Thanks for writing this!

docs/docs/reference/release-notes/v2-maintenance-plan.md Outdated Show resolved Hide resolved
docs/docs/reference/release-notes/v2-maintenance-plan.md Outdated Show resolved Hide resolved
docs/docs/reference/release-notes/v2-maintenance-plan.md Outdated Show resolved Hide resolved
docs/docs/reference/release-notes/v2-maintenance-plan.md Outdated Show resolved Hide resolved
@meganesu meganesu added type: documentation An issue or pull request for improving or updating Gatsby's documentation and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Apr 21, 2021
@pragmaticpat
Copy link
Contributor Author

@meganesu - mind taking one more pass on this? I think it's in good shape now for an initial iteration of the published content. Thanks!

@pragmaticpat
Copy link
Contributor Author

Left a few comments! Overall, this is in good shape.

One thing that I think is missing is setting expectations for how we want users to engage with us if they run into problems (with v2.32 or with v3). Mainly to clarify how we want them to reach out (open an issue, email support) and what kind of support they can expect from us. I'm assuming there would be different expectations for active vs. maintenance support.

I'm not sure if you've opened a PR in mansion yet, but you'll also need to add this file to the docs sidebar to get it to display in the hierarchy.

Thanks for writing this!

Ah - I didn't yet open the PR in mansion to get it in the sidebar. Thanks for the tip! Will do that then close this comment.

@wardpeet wardpeet merged commit b1905b1 into master Apr 23, 2021
@wardpeet wardpeet deleted the v2-maintenance-plan branch April 23, 2021 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation An issue or pull request for improving or updating Gatsby's documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants