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

first draft 5.1 release notes #1442

Merged
merged 7 commits into from
May 21, 2019
Merged

first draft 5.1 release notes #1442

merged 7 commits into from
May 21, 2019

Conversation

rrelyea
Copy link
Contributor

@rrelyea rrelyea commented May 15, 2019

@karann-msft - This should be ready to ship before 5/21. Can you please add additional things to this page to make it shipable and run with this.

All - I've done a walk through all closed issues in 5.1 milestone, and added tags as approriate, and tweaked the title to be customer ready. Please do a quick review.
Anything missing from 5.1.0 that we should be telling the world about?

@karann-msft
Copy link
Contributor

Docs Build status updates of commit a91526d:

✅ Validation status: passed

File Status Preview URL Details
docs/release-notes/Index.md ✅Succeeded View
docs/release-notes/NuGet-5.1-RTM.md ✅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.

nkolev92
nkolev92 previously approved these changes May 15, 2019
@anangaur
Copy link
Member

Created a PR against this branch to reorder the issues list to put Features then DCRs and then Bugs. Also changed the bold topics (**) to ## topics.

@anangaur
Copy link
Member

I also feel the Features tab should just be removed and these should be covered in "Summary: What's New in 5.1" if its a value item for customers. Rest should move to DCRs/Bugs.


* Make Tizen 6 map to NetStandard 2.1 - [#7773](https://github.com/NuGet/Home/issues/7773)

**Feature:**
Copy link
Member

Choose a reason for hiding this comment

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

Unless these are items that's a feature for end customers i.e. something net new they can/should try, they shouldn't be called features. And in general features should move to "Summay:What's new in 5.1?"

Reordered to put features first follwed by DCR and then Bugs
@karann-msft
Copy link
Contributor

Docs Build status updates of commit ae9794b:

✅ Validation status: passed

File Status Preview URL Details
docs/release-notes/Index.md ✅Succeeded View
docs/release-notes/NuGet-5.1-RTM.md ✅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.

@karann-msft
Copy link
Contributor

Docs Build status updates of commit d9f32ee:

✅ Validation status: passed

File Status Preview URL Details
docs/release-notes/Index.md ✅Succeeded View
docs/release-notes/NuGet-5.1-RTM.md ✅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.

@karann-msft
Copy link
Contributor

Docs Build status updates of commit 03c82b2:

✅ Validation status: passed

File Status Preview URL Details
docs/release-notes/Index.md ✅Succeeded View
docs/release-notes/NuGet-5.1-RTM.md ✅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.

@karann-msft karann-msft merged commit c7bbaa8 into master May 21, 2019
@karann-msft karann-msft deleted the dev-rrelyea-relnotes5.1.0 branch June 7, 2019 20:20
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.

4 participants