Replies: 2 comments 6 replies
-
That's why we have consumer-facing release notes on the website. See https://fluentassertions.com/releases/ |
Beta Was this translation helpful? Give feedback.
-
I know it's in no way intended, but comparing us to MSDN is a little unfair in terms of manpower/resources. As Dennis mentions, to keep things easier for us, documentation/examples goes in with the PR changing the code. There is definitely room for improvement in the auto-generated GitHub release notes. Seems we can configure the auto-generated GitHub release notes to group the changes by labels. |
Beta Was this translation helpful? Give feedback.
-
I was reading the latest release notes and noticed this there:
I'd like to say that, at least from a library consumer perspective, I'm only interested in library-related updates when reading the release notes. And I'm not saying that to feel entitled or anything: I'd assume most of the community would agree.
At the same time, I fully understand you guys wanting to keep track of everything that happens on the site side as well.
With that in mind, have you considered splitting site and library concerns into perhaps 2 different repositories, each with their own release schedules/versions/etc?
Beta Was this translation helpful? Give feedback.
All reactions