Alex. How are we supposed to use this report? Release notes should be designed in such a way, that the most important features are highly visible, while minor changes are either skipped at all, or shown aside, as they have little to no value for users. If someone is interested in all fixed tickets, we can give a link to JIRA report. Moreover, some fixes must be even hidden from users, e.g. security-related stuff.
That said, I am not quite sure I understand the purpose of this reporting. It is not user-friendly. Vladimir. On Wed, Aug 2, 2017 at 4:57 PM, Aleksey Chetaev <alex.chet...@gmail.com> wrote: > Igniters, > > Started 2.0 we generated manually Jira based release notes with all new > improvements and fixed bugs. > f.e(https://ignite.apache.org/releases/2.1.0/release_notes.html). I > created > new class in ignite-tools for we can do it automatically using IDE or > TeamCity. Class using JSON template for create release notes. In template > we > can setup Jira servers with credentials and filters for each release notes > section. > Please see pull request: https://github.com/apache/ignite/pull/2379 may be > we can merge this to Ignite for improve our release process? > > Kind regards > Aleksey Chetaev. > > > > -- > View this message in context: http://apache-ignite- > developers.2346864.n4.nabble.com/Release-notes-tools-for- > Ignite-releases-tp20377.html > Sent from the Apache Ignite Developers mailing list archive at Nabble.com. >
