On Thu, 10 Feb 2022 at 02:04, Tamás Cservenák <[email protected]> wrote:
> Howdy, > > Yes, looks good, but one thing bothers me: > Does this mean that Maven projects -- if release-drafter is to be used -- > will have their release notes stored and accessible in their mirror > repositories only? > I do not see this as a mandatory part of the release process but a nice feature to add. (it's 98,7802% automatic so do not need much extra work) And especially for plugins because these days a lot of people use github and dependabot. So they receive such dependabot PR to update a maven plugin [1]. Reading this it's hard to figure out what has changed and why it's broken now with this upgrade (if you are lucky to know it's broken because you have configured some checks with some CI tooling). Then you google maven-compiler 3.9.0 and you find a link to a mailing list archive entry [2] well at this stage it is not too bad you found some official email from Apache Maven folks and you have a link to https://maven.apache.org/plugins/maven-compiler-plugin/ Where are there any details on the last release? (I'm not pointing anybody as I'm definitely guilty as well regarding the lack of documentation :) ) At this stage ok let's look at the email content. Oh there are some cryptic `[MCOMPILER-359]` (yup it's text email so no links) Not sure most of the users know what to do with that. I know `google it` :) but still takes more time than a click Anyway I wouldn't make it mandatory especially for some "obscure" shared components only used by our plugins. but anyway if any volunteers for that why not. /Olivier [1] https://github.com/cometd/cometd/pull/1125 [2] https://lists.apache.org/thread/9j2yf1771qwkhcrgpc22nf5gqffxq8cf > > T > > On Wed, Feb 9, 2022 at 4:57 PM Slawomir Jaranowski <[email protected] > > > wrote: > > > Looks great. > > > > To avoid all PR in the first release we can add an empty release note for > > the latest release tag and then the new release draft should contains > only > > PR from the latest release not all. > > > > śr., 9 lut 2022 o 05:10 Olivier Lamy <[email protected]> napisał(a): > > > > > Hi > > > Github has a feature to attach a release note to tag/release. > > > The content is then used when dependabot generates his famous PR all > > > over the world!! (yup a maven plugin generates a lot!!) > > > Our current content is not very user friendly.... > > > > > > While preparing the maven-compiler-plugin new release I have made some > > > tests using release-drafter tool [1]. > > > This generates the content here: > > > https://github.com/apache/maven-compiler-plugin/releases > > > The release notes will automatically contains only content from PRs (PR > > > must have a label to appear in a dedicated section otherwise they will > be > > > in the top, see mapping label/section here [2]) > > > This mapping is a default which can be shared between all project so > the > > > configuration is very simple see [3]. > > > Please note the first time it's used the first release will > > > contain everything (all PRs) from the start as there is no first > release. > > > The process is manual at the end, after all of our release process > steps, > > > you just need to go to GH ui then publish the release (manual. > > > modifications still possible). > > > > > > comments? thoughts? complaints :)? > > > > > > cheers > > > Olivier > > > > > > PS: if you want to use this be sure to modify manually the content > before > > > the publish as the content is regenerated for every merge PR > > > > > > [1] https://github.com/release-drafter/release-drafter > > > [2] > > > > > > > > > https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml > > > [3] > > > > > > > > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml > > > and > > > > > > > > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml > > > > > > > > > -- > > Sławomir Jaranowski > > >
