Release notes

[MehdiK]

Some suggestions on top of #96

[mwhelan]

These changes are a big improvement.

[JakeGinnivan]

These breaking changes should be added to a readme.txt shipped with the NuGet package

[MehdiK]

Good idea. I think we should just package the entire release-notes file with the nuget so users know what's being added over time. Thoughts?

[mwhelan]

Yeah, makes sense to stick to the one file to maintain.

On Wed, Apr 9, 2014 at 9:26 AM, Mehdi Khalili notifications@github.comwrote:

In release-notes.md:

@@ -1,4 +1,27 @@
-###In development
+##V4 In Development
+
+####Improvements

• - #61 & #62 - rationalized BDDfy namespaces to require less namespaces for some features and to make features more discoverable. Breaking Change

Good idea. I think we should just package the entire release-notes file
with the nuget so users know what's being added over time. Thoughts?

Reply to this email directly or view it on GitHubhttps://github.com//pull/99/files#r11426714
.

[JakeGinnivan]

Build could just copy the releasenotes to readme.txt?

Maybe even insert a welcome to BDDfy thing above the release notes as well

[MehdiK]

tbh I have a fundamental issue with readme in nuget packages and that is they overwrite each other (or at least did the last time I checked)! BDDfy used to have a readme called bddfy-readme.md.

I think/thought having a readme in the nuget is a good idea; but it's also maintenance nightmare in that any time there was a breaking change I had to update a few files around the place.