.NET 3.4.1 Release notes

[jeffrymorris]

No description provided.

[dnault]

LGTM.

I can't remember whose idea this was (Richard? Hakim? Maria?), but over in Java-land we've been trying to phrase the release notes as positives instead of negatives. In other words, describing the improvement instead of the flaw.

For example, instead of "Search: Min function throws an exception if the argument is > 0", we could say:

When using a DisjunctionQuery in a full-text search, it's now possible to specify the minimum number of sub-queries that must be satisfied. (Previously, DisjunctionQuery.Min() would always throw ArgumentOutOfRangeException.)

[dnault]

NIT: This is information-free :-) Omit it if you want.

[RichardSmedley]

Thanks David - this bit is as much visual pause as orientation, for those skimming quickly.

[dnault]

NIT: If the fix was to change/disable the test, is it release note-worthy?

[RichardSmedley]

LGTM.

I can't remember whose idea this was (Richard? Hakim? Maria?), but over in Java-land we've been trying to phrase the release notes as positives instead of negatives. In other words, describing the improvement instead of the flaw.

Thanks David - we've asked for this before, but the .NET team doesn't have the resources at present.

One workaround we've discussed with @raycardillo is a compulsory release notes field in JIRA, so that the text can be filled out when closing an issue - whilst the knowledge is fresh in the engineer's mind.