Bug 502476

Description Wayne Beaton 2016-09-28 14:04:00 EDT

This may be a duplicate of Bug 412317.

I propose that we make a release notes page that simple lists the bugs that were addressed in any particular release.

We actually have most of the infrastructure for this already. When a release record's version matches the name of a target milestone in Bugzilla, we are able to automatically generate a  page of issues (e.g. [1]) directly out of Bugzilla (with no further input from the project team). For any simultaneous release instance, we have a list of all release records for participating projects.

It should be relatively simple to generate a page that aggregates this information for all projects in a single location.

To make this work, however, we'd need project teams to actually use target milestones in Bugzilla (we should also address Bug 482531 to include GitHub issues in the list).

Should we make it a strict _requirement_ for participation in the simultaneous release? Frankly, setting target milestones seems like a sort of minimal kind of planning that project teams really should be doing anyway.

I can't help but notice that even the Eclipse project didn't create a target milestone for the Neon.1 release (or a record for the service release). Is making this a requirement too onerous?

This feels like a really obvious sort of thing that we should be doing.

We might be able to do something automatic(ish) with Git commits, except that there is no consistent means of associating a commit with a particular release. We can probably make really good guesses with dates, but that's about as close as we can get without coming up with some sort of rules for the consistent use of branches or tags.

[1] https://projects.eclipse.org/projects/eclipse/releases/4.7.0/bugs