One could also have a flat list of contributors below the changelist
similar to Gradle's release notes:
https://docs.gradle.org/current/release-notes.html
This list could include authors of skipped PRs.

On Mon, Nov 4, 2019 at 9:16 PM Daniel Beck <[email protected]> wrote:

>
> > On 4. Nov 2019, at 20:21, Oleg Nenashev <[email protected]> wrote:
> >
> > It needs some work so that we mention skipped changelog entries, but it
> could be already a good start.
>
> How we solve *this* is the most important part and determines whether this
> is an overall beneficial change or not.
>
> Right now, we do not actually record everything in the changelog:
>
> - Changes that don't make it into the jenkins.war are skipped, such as
> Javadoc changes, Jenkinsfile changes, or tests. There's no reason to
> mention them, because they're not part of what users experience.
> - Minor changes like updated log messages, few updated localized messages,
> minor code cleanups without behavior change, and similar, are skipped.
> People's attention is limited, and a changelog that contains _everything_
> ends up being really long. This is obviously subjective.
>
> As an example, there were 8 visible changelog entries for 2.199, and
> another 13 that weren't. I wouldn't want to read a 21 entry changelog for a
> weekly release, and I doubt anyone would.
>
> Once we're starting to credit contributors in the changelog, how will that
> change? Being credited in the changelog could energize contributors -- and
> having their change skipped since it didn't make some arbitrary bar might
> upset them. Would we include more changelog entries just to make them
> happy, to the detriment of changelog consumers?
>
> Even if you manage to find a nice, objective rule to apply here (which I
> expect to be impossible while skipping any changes that make it into
> jenkins.war) -- how will you solve this problem for the LTS.1 changelog
> with its section "Notable changes since 2.xxx.3", that only mentions
> perhaps 20% of all changes that show up in weekly changelogs?
>
>
> Now, perhaps people won't care whether their changes are notable enough to
> make the (LTS) changelog and are simply happy when they do show up, and I'm
> completely wrong about this. I simply fear that I'm not.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ADDFE121-6293-47A5-AA57-427E12F8C86B%40beckweb.net
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CABFvdGpTixRCSd7V3gu4_gQm1jW87Z%2BobkF%3DgDvmse1Pk9wumA%40mail.gmail.com.

Reply via email to