Looks like that solves that problem. Probably wouldn't be a bad idea to include that list in the release posts as well as link to changes.txt? At the very least it will make us a bit more careful about assigning fix versions (maybe).
On 1 November 2017 at 00:36, Michael Shuler <mich...@pbandjelly.org> wrote: > On 10/31/2017 07:17 PM, kurt greaves wrote: > > It's usually pretty clear what is a fix in the changes log but they > > definitely require checking. However I'd say putting more boilerplate in > > the changes log isn't really necessary and would be hard to enforce. If > we > > could generate a report with this information from JIRA with desired > > information would be better (e.g all ticket names, type, maybe even > > labels). I'd hope JIRA has this functionality... > > > > It does have release notes that is split up by issue type: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12310865&version=12336842 > > -- > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
