I like the flag, it would help cut down on the work involved in creating the release notes. Eventually, we may want to group the fixes "by component" in the release notes.
-g- On Mon, May 20, 2019 at 4:28 AM Ilya Kasnacheev <ilya.kasnach...@gmail.com> wrote: > Hello! > > I think it definitely makes sense to have Release Notes field in JIRA > tickets (start using it if it is already present?). Not sure about the > flag. > > Regards, > -- > Ilya Kasnacheev > > > пн, 20 мая 2019 г. в 13:23, Dmitriy Pavlov <dpav...@apache.org>: > > > Hi Ignite Developers, > > > > Kindly Reminder, please review the proposed changes and share your > vision. > > I would appreciate if this change will be approved by community members, > > but not via silence. > > > > Sincerely > > Dmitriy Pavlov > > > > вт, 14 мая 2019 г. в 15:19, Dmitriy Pavlov <dpav...@apache.org>: > > > > > Hi Igniters, > > > > > > During the preparation of release candidate 2.7.5, I’ve missed the > > > development of Release notes for it, and this caused delay for a vote. > > > > > > I want to suggest simple changes in our documentation process. Some > time > > > ago Artem B. proposed similar for the doc, but I would like to adapt it > > for > > > release notes. > > > > > > Let us > > > - Enrich Ignite flags with 'Release Notes required' flag (default is, > as > > > always, true) > > > - Add field 'Release Notes' to Ignite project. > > > > > > All tickets with empty Release Notes fields but with flag set may be > > > checked with contributor if it needs to be mentioned in > > RELEASE_NOTES.txt. > > > > > > If we agree on these changes, I’ll ask infra to add these fields in 3 > > > days. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > > > >
