ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: [Discussion] Documentation process improvement: Release notes
Date Mon, 20 May 2019 11:28:19 GMT
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 <dpavlov@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 <dpavlov@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
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message