Skip to content

Conversation

rpetrusha
Copy link
Contributor

.NET Core breaking changes

Fixes #11566

//cc @terrajobst

@rpetrusha rpetrusha requested a review from mairaw as a code owner June 12, 2019 23:18
@rpetrusha rpetrusha self-assigned this Jun 12, 2019
Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

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

LGTM @rpetrusha. Left some comments for you to consider.
I'll do a new review after some of the changes I've requested are implemented.

ms.date: 06/10/2019
---
# Breaking change categories

Copy link
Contributor

Choose a reason for hiding this comment

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

should you add an intro saying what this article is about?


A particular change can affect compatiiblity in a number of ways. These fall into five categories:

## Behavioral change
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be a numbered list instead?

@mairaw
Copy link
Contributor

mairaw commented Jun 13, 2019

There are also some warnings on the build report that you should take a look.

Ron Petrusha and others added 2 commits June 14, 2019 08:51
Co-Authored-By: Maira Wenzel <mairaw@microsoft.com>
@dotnet-bot
Copy link
Contributor

Docs Build status updates of commit 371ed58:

✅ Validation status: passed

File Status Preview URL Details
docs/core/compatibility/categories.md ✅Succeeded View
docs/core/compatibility/index.md ✅Succeeded View
docs/toc.yml ✅Succeeded View

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@@ -0,0 +1,43 @@
---
title: Breaking change categories - .NET Core
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't need the - .NET Core on the title.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, it's better to have @Thraka - that's why I suggested to add it. It's part of the SEO guidelines to have a brand suffix.
https://review.docs.microsoft.com/en-us/new-hope/quality/catstestcases/seo-rule?branch=master#title-metadata---title-suffix

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm confused then 😄 I thought this is automatically appended via the docfx file??

Copy link
Contributor

Choose a reason for hiding this comment

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

Depends on the section of the docs. Not for every folder.

@rpetrusha
Copy link
Contributor Author

This is ready for another review, @mairaw.

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

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

Looks good @rpetrusha but left a few more suggestions for you before you merge

---
# Breaking change categories

*Compatibility* refers to the ability to compile or execute code on a version of a .NET implementation other than the one with which the code was originally developed. Changes between versions can affect compatibility in A particular change can affect compatibility in six different ways. The [individual kinds of changes that are considered when evaluating compatibility](index.md) fall into the first five categories. These are:
Copy link
Contributor

Choose a reason for hiding this comment

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

can affect compatibility in A particular change -> it seems you forgot part of the sentence here?


6. Forward compatibility

Forward compatibility refers to the ability of an existing consumer of an API to run against and behave the way as an older version. If a consumer is not able to run or behaves differently against an older version of the API, the API is *forward incompatible*.
Copy link
Contributor

Choose a reason for hiding this comment

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

"behave the way as an older version" reads a bit funny


*Compatibility* refers to the ability to compile or execute code on a version of a .NET implementation other than the one with which the code was originally developed. Changes between versions can affect compatibility in A particular change can affect compatibility in six different ways. The [individual kinds of changes that are considered when evaluating compatibility](index.md) fall into the first five categories. These are:

1. Behavioral change
Copy link
Contributor

Choose a reason for hiding this comment

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

wondering if it would be better to have these as H2s


- It breaks late-bound scenarios such as the late binding feature in Visual Basic and [dynamic](../../csharp/language-reference/keywords/dynamic.md) in C#.

- It breaks [source compatibility](categories.md#source-compatibility) when developers use [named arguments](../../csharp/programming-guide/classes-and-structs/named-and-optional-arguments.md#named-arguments).
Copy link
Contributor

Choose a reason for hiding this comment

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

This anchor is broken

Co-Authored-By: Maira Wenzel <mairaw@microsoft.com>
@rpetrusha
Copy link
Contributor Author

Thanks for the thorough review once again, @mairaw!

@rpetrusha rpetrusha merged commit e394f9d into dotnet:master Jun 20, 2019
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.

Document the bar for breaking changes
4 participants