I don't think the warning about release drafter really affects jenkins. Its
all open source and public anyways.

+1 to standardising on using github releases. I started letting release
drafter work and then copy the release notes to confluence just for
backwards compability

On Thu, May 23, 2019 at 8:16 AM Jesse Glick <[email protected]> wrote:

> +1 from me as well. I guess we would consider it a separate though
> related effort to actually standardize use of Release Drafter, so that
> plugins.jenkins.io is able to obtain changelogs from the GitHub
> release metadata rather than Confluence.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1gg%3DzKKPUvgajeDMznLeBHDh6AZa-UPfa%3Dgmk0vtKJpQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAgr96L9pk4xLdkH-2wCkT6TquREHXZ2_3dvF%3Dy9VyYG%2BOQ2gA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to