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

DOCSP-45586: Remove What's New breaking changes #80

Merged

Conversation

norareidy
Copy link
Collaborator

@norareidy norareidy commented Nov 21, 2024

Pull Request Info

PR Reviewing Guidelines

This PR removes repeated breaking change information by taking them out of What's New. It should be merged before the 4.0 release tickets.

JIRA - https://jira.mongodb.org/browse/DOCSP-45586
Staging:
https://deploy-preview-80--docs-cpp.netlify.app/whats-new/
https://deploy-preview-80--docs-cpp.netlify.app/upgrade/

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Did you run a spell-check?
  • Did you run a grammar-check?
  • Are all the links working?
  • Are the facets and meta keywords accurate?

Copy link

netlify bot commented Nov 21, 2024

Deploy Preview for docs-cpp ready!

Name Link
🔨 Latest commit e849e64
🔍 Latest deploy log https://app.netlify.com/sites/docs-cpp/deploys/673faba6440c470008af8040
😎 Deploy Preview https://deploy-preview-80--docs-cpp.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@eramongodb eramongodb mentioned this pull request Nov 21, 2024
5 tasks
Copy link
Collaborator

@mcmorisi mcmorisi left a comment

Choose a reason for hiding this comment

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

LGTM with a quick suggestion!

@@ -66,12 +66,64 @@ and upgrade versions.
If you're upgrading the {+driver-short+} from version 3.0 to version 3.10,
address all breaking changes listed for versions 3.1 to 3.10, if any.

Types of Breaking Changes
Copy link
Collaborator

Choose a reason for hiding this comment

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

Question/Suggestion: should we change the .. contents:: component to be depth level 2? Each of the main headers have a few subsections so might be helpful to include those in the page ToC. If changing this results in the ToC becoming too lengthy/unwieldy, feel free to leave

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I changed depth to 2 originally, but it did make the TOC look overly complicated (since the subheaders have long titles). So I think I'll leave as is

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

nvm changed back to 2 after restructuring!

Copy link
Collaborator

@eramongodb eramongodb Nov 21, 2024

Choose a reason for hiding this comment

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

Possibly related (I do not fully understand the depth level discussion), I am in favor of removing the "Breaking Change Definition" and "Types of Breaking Changes" headers entirely while preserving the remaining content as-is, such that the current contents of each section just become contents of "Overview".

On this page

  • Overview
  • Breaking Changes
    • Version 4.0
    • ...

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hm, Overview gets pretty long and disorganized if I remove those subheaders.

Copy link
Collaborator

Choose a reason for hiding this comment

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

If so, I am fine with leaving them as-is.

@eramongodb eramongodb self-requested a review November 21, 2024 21:05
source/upgrade.txt Outdated Show resolved Hide resolved
@@ -66,12 +66,64 @@ and upgrade versions.
If you're upgrading the {+driver-short+} from version 3.0 to version 3.10,
address all breaking changes listed for versions 3.1 to 3.10, if any.

Types of Breaking Changes
Copy link
Collaborator

@eramongodb eramongodb Nov 21, 2024

Choose a reason for hiding this comment

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

Possibly related (I do not fully understand the depth level discussion), I am in favor of removing the "Breaking Change Definition" and "Types of Breaking Changes" headers entirely while preserving the remaining content as-is, such that the current contents of each section just become contents of "Overview".

On this page

  • Overview
  • Breaking Changes
    • Version 4.0
    • ...

source/upgrade.txt Show resolved Hide resolved
source/upgrade.txt Outdated Show resolved Hide resolved
source/upgrade.txt Show resolved Hide resolved
@norareidy norareidy requested a review from eramongodb November 21, 2024 22:01
source/upgrade.txt Show resolved Hide resolved
@@ -66,12 +66,64 @@ and upgrade versions.
If you're upgrading the {+driver-short+} from version 3.0 to version 3.10,
address all breaking changes listed for versions 3.1 to 3.10, if any.

Types of Breaking Changes
Copy link
Collaborator

Choose a reason for hiding this comment

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

If so, I am fine with leaving them as-is.

@norareidy norareidy merged commit e53a9f3 into mongodb:master Nov 21, 2024
4 of 5 checks passed
@norareidy norareidy deleted the DOCSP-45586-remove-breaking-changes branch November 21, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants