Reduce friction for Release Notes maintenance - release notes pack support

[mteper]

Too many packages do not include release notes, and I speculate that the reason lies in the friction involved in doing so, as the developer is required to actively maintain the .nuspec file. Many projects build directly from the VS project bypassing .nuspec altogether.

A few changes would improve this situation:

• add support for pulling in content from an external file
• have nuget pack look for releasenotes.md
• add support for a standard changelog URL
• add parameter to nuget pack for passing in changelog URL

maintainer edit

• Package Manager UI side - Release Notes in the Package Manager UI  #1823

[ashmind]

ReleaseNotes.md would be great, especially considering ASP.NET's project.json does not allow newlines other than \r\n, which is unusable for any large-ish metadata.

Alternatively -- sections from ReadMe.md for both Description and Release Notes (description has same problem with project.json).

[leppie]

Allow release notes to be constructed from commits to git or TFS, etc.

[jrossstocholm]

I strongly second this - the friction to create the release notes package configuration is too high.

We build our nuget packages from Visual Studio Online, and I would actually much prefer to simply be able to add release notes via a command line parameter. In VSO we have already set up a build parameter with version number information, so we configure the Nuget Packager build step with "Nuget arguments"

-version $(NugetVersion)

It would be great to be able to add simple text like

-releaseNotes $(<insert build variable here>)

[yishaigalatzer]

@NickCraver has provided more insights and some good ideas. These should be addressed when we handle this suggestion. #1734

[304NotModified]

In the recent updates (NLog, yeah we're listed #1734) we do add the changelog, but we found out it's pretty useless as the Visual Studio client isn't even showing the changelog...

edit: I see that's #1823

[rmarinho]

Any progress on this?