<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 4, 2019 at 2:22 AM Darran Lofthouse <<a href="mailto:darran.lofthouse@jboss.com">darran.lofthouse@jboss.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Very nice, maybe when a feature gets close to being merged developers could also consider writing a blog for their new feature and adding a link to this section - it would mean we would have quite a comprehensive set of information available at release time.</div></blockquote><div><br></div><div>+1 that is a good idea as well.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 3, 2019 at 10:13 PM James Perkins <<a href="mailto:jperkins@redhat.com" target="_blank">jperkins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello All,<div>I've merged a <a href="https://github.com/wildfly/wildfly-proposals/pull/163" target="_blank">PR</a> [<a href="https://github.com/wildfly/wildfly-proposals/pull/163" target="_blank">1</a>] for the proposal template which includes a selection for release notes. Currently we tend to do release notes when the release is ready. This causes the writer to have to go back and look up features that should have release notes. In some cases the writer may not really know much about the feature and has to make them up by reading the proposal. It would be helpful if the SME wrote the release notes and all the writer has to do is copy and paste them.<br><div><br></div><div>I do realize not all features will have or require release notes so this isn't a required section. However if you feel you'd like your feature in the release notes adding the content to the proposal will be very helpful.</div><div><br></div><div>Thanks in advance.</div><div><br></div><div>[1]: <a href="https://github.com/wildfly/wildfly-proposals/pull/163" target="_blank">https://github.com/wildfly/wildfly-proposals/pull/163</a><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div></div></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div></div>