[wildfly-dev] Release Notes in Proposal Documents

[James Perkins]

On Fri, Oct 4, 2019 at 2:22 AM Darran Lofthouse <darran.lofthouse at jboss.com>
wrote:

> 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.
>

+1 that is a good idea as well.


>
>
> On Thu, Oct 3, 2019 at 10:13 PM James Perkins <jperkins at redhat.com> wrote:
>
>> Hello All,
>> I've merged a PR <https://github.com/wildfly/wildfly-proposals/pull/163>
>>  [1 <https://github.com/wildfly/wildfly-proposals/pull/163>] 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.
>>
>> 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.
>>
>> Thanks in advance.
>>
>> [1]: https://github.com/wildfly/wildfly-proposals/pull/163
>>
>> --
>> James R. Perkins
>> JBoss by Red Hat
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>

-- 
James R. Perkins
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20191004/bf3c9aa5/attachment.html