Re: Release notes tools for Ignite releases

If the solution is positive, can anyone see my pull request? 2017-08-03 4:28 GMT+03:00 dsetrakyan [via Apache Ignite Developers] < ml+s2346864n20403...@n4.nabble.com>: > Agree with Denis. I think that we should treat it as a starting point for > the release notes, and further update it before rel

Re: Release notes tools for Ignite releases

Agree with Denis. I think that we should treat it as a starting point for the release notes, and further update it before releases. On Wed, Aug 2, 2017 at 10:58 PM, Denis Magda wrote: > Guys, > > We're on the same page that the page has to look more colorful and > informative. This is exactly wh

Re: Release notes tools for Ignite releases

Guys, We're on the same page that the page has to look more colorful and informative. This is exactly why Spark's page was given as an example. However, I like the template generated by Alex script in a sense that you already have something to start work with. Go ahead and remove redundant ticket

Re: Release notes tools for Ignite releases

Alex, This is not only about the issue types. Release notes is the face of our product. Generating it from JIRA has several problems which are unresolvable IMO: 1) Tickets are created by many dozens people, so there could be typos, linguistic errors, etc. 2) Ticket descriptions often inconclusive

Re: Release notes tools for Ignite releases

Vladimir, I agree that page not perfect now. I think, problem in Jira issue types. A lot of new features or improvements created as task and often we don't use sub-task for depended issues. I can be wrong, but committer who prepared release can't manually create this page, we need have some tools.

Re: Release notes tools for Ignite releases

JIRA = report from JIRA ср, 2 авг. 2017 г. в 21:35, Vladimir Ozerov : > Denis, > > This page works exactly how I suggested in the beginning of that thread: > manually crafted notes on most important features + link to JIRA report to > see all closed tickets. > > We already have manually crafted a

Re: Release notes tools for Ignite releases

Denis, This page works exactly how I suggested in the beginning of that thread: manually crafted notes on most important features + link to JIRA report to see all closed tickets. We already have manually crafted any properly grouped release notes. All we need is to make them a bit more verbose, a

Re: Release notes tools for Ignite releases

Vladimir, The goal is to have a page like that: https://spark.apache.org/releases/spark-release-2-1-0.html where a user can go and see all the changes incorporated in the release. The header of the file can be custom - you can list m

Re: Release notes tools for Ignite releases

Alex, In AI 2.1 we fixed several hundreds issues. Why do you think there is a single person interested in reviewing all of them? E.g. we added new JDBC driver. I do not see it in the list of major features, neither I need to know that this task was split into 20 smaller sub tasks, each of which ar

Re: Release notes tools for Ignite releases

Vladimir, We have links to release notes on download page: https://ignite.apache.org/ download.cgi. For be user-friendly we added header with description about most interested features in release and near list of issues. If we want skip minor or another issues we can use Jira labels and skip issue

Re: Release notes tools for Ignite releases

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