You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Nicolas Malin via dev <de...@ofbiz.apache.org> on 2026/10/16 12:47:45 UTC
Release process -> Release Note and Pull Request
Hello,
I current work to prepare the publication of the release24.09.08 on our
website (ofbiz.apache.org) to be ready when the process release will be
ok and I'm in front of the situation to build the release note with the
new commit process.
At this time we build the release note from jira [1] :
> Announcing the Release
>...
>Create an html page with the release notes (generated by Jira)
> In Jira, mark the version as "released" and create a new
version for the next release
> Add the information about the release to the release
history page: http://www.apache.org/dist/ofbiz/
<http://www.apache.org/dist/ofbiz/>
Like this we obtains the following page [2].
Now If we follow this process, all Github Pull Request without jira
issue would not be present on the release note. By the way, I checked
how with github we can create the release not [3] and tried a draft [4]
(like Jacopo for the 24.09.07).
After that,I would tend to favor to use the release note generate by
Github without Bump commit. I realized a try on my ofbiz-site repo [5] [6].
Do you have any other idea/proposal ?
At this end, I'll update our release process on our wiki once everything
is clear
Nicolas
[1]
https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
[2] https://ofbiz.apache.org/release-notes/24.09.07.html
[3]
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
[4]
https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
[5]
https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
[6]
https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
Re: Release process -> Release Note and Pull Request
Posted by Jacopo Cappellato <ja...@gmail.com>.
Hi Nicolas,
My preference is for switching to the release notes created from GitHub
pull requests as you did with [4].
Jacopo
On Fri, Oct 16, 2026 at 2:47 PM Nicolas Malin via dev <de...@ofbiz.apache.org>
wrote:
> Hello,
>
> I current work to prepare the publication of the release24.09.08 on our
> website (ofbiz.apache.org) to be ready when the process release will be
> ok and I'm in front of the situation to build the release note with the
> new commit process.
>
> At this time we build the release note from jira [1] :
>
> > Announcing the Release
> >...
> >Create an html page with the release notes (generated by Jira)
> > In Jira, mark the version as "released" and create a new
> version for the next release
> > Add the information about the release to the release
> history page: http://www.apache.org/dist/ofbiz/
> <http://www.apache.org/dist/ofbiz/>
>
> Like this we obtains the following page [2].
> Now If we follow this process, all Github Pull Request without jira
> issue would not be present on the release note. By the way, I checked
> how with github we can create the release not [3] and tried a draft [4]
> (like Jacopo for the 24.09.07).
>
> After that,I would tend to favor to use the release note generate by
> Github without Bump commit. I realized a try on my ofbiz-site repo [5] [6].
> Do you have any other idea/proposal ?
>
> At this end, I'll update our release process on our wiki once everything
> is clear
>
> Nicolas
>
> [1]
>
> https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
> [2] https://ofbiz.apache.org/release-notes/24.09.07.html
> [3]
>
> https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
> [4]
>
> https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
> [5]
>
> https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
> [6]
>
> https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
>
Re: Release process -> Release Note and Pull Request
Posted by Jacques Le Roux via dev <de...@ofbiz.apache.org>.
Hi,
Oops, I got a 404 at https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
Jacques
Le 16/10/2026 à 14:47, Nicolas Malin via dev a écrit :
> Hello,
>
> I current work to prepare the publication of the release24.09.08 on our website (ofbiz.apache.org) to be ready when the process release will be ok
> and I'm in front of the situation to build the release note with the new commit process.
>
> At this time we build the release note from jira [1] :
>
> > Announcing the Release
> >...
> >Create an html page with the release notes (generated by Jira)
> > In Jira, mark the version as "released" and create a new version for the next release
> > Add the information about the release to the release history page: http://www.apache.org/dist/ofbiz/ <http://www.apache.org/dist/ofbiz/>
>
> Like this we obtains the following page [2].
> Now If we follow this process, all Github Pull Request without jira issue would not be present on the release note. By the way, I checked how with
> github we can create the release not [3] and tried a draft [4] (like Jacopo for the 24.09.07).
>
> After that,I would tend to favor to use the release note generate by Github without Bump commit. I realized a try on my ofbiz-site repo [5] [6].
> Do you have any other idea/proposal ?
>
> At this end, I'll update our release process on our wiki once everything is clear
>
> Nicolas
>
> [1]
> https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
> [2] https://ofbiz.apache.org/release-notes/24.09.07.html
> [3] https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
> [4] https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
> [5] https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
> [6] https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
Re: Release process -> Release Note and Pull Request
Posted by Anahita Goljahani <an...@gmail.com>.
Hi Nicolas,
+1 for using GitHub release notes.
Thanks
Anahita
Il giorno ven 16 ott 2026 alle ore 14:48 Nicolas Malin via dev
<de...@ofbiz.apache.org> ha scritto:
>
> Hello,
>
> I current work to prepare the publication of the release24.09.08 on our
> website (ofbiz.apache.org) to be ready when the process release will be
> ok and I'm in front of the situation to build the release note with the
> new commit process.
>
> At this time we build the release note from jira [1] :
>
> > Announcing the Release
> >...
> >Create an html page with the release notes (generated by Jira)
> > In Jira, mark the version as "released" and create a new
> version for the next release
> > Add the information about the release to the release
> history page: http://www.apache.org/dist/ofbiz/
> <http://www.apache.org/dist/ofbiz/>
>
> Like this we obtains the following page [2].
> Now If we follow this process, all Github Pull Request without jira
> issue would not be present on the release note. By the way, I checked
> how with github we can create the release not [3] and tried a draft [4]
> (like Jacopo for the 24.09.07).
>
> After that,I would tend to favor to use the release note generate by
> Github without Bump commit. I realized a try on my ofbiz-site repo [5] [6].
> Do you have any other idea/proposal ?
>
> At this end, I'll update our release process on our wiki once everything
> is clear
>
> Nicolas
>
> [1]
> https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
> [2] https://ofbiz.apache.org/release-notes/24.09.07.html
> [3]
> https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
> [4]
> https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
> [5]
> https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
> [6]
> https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
Re: Release process -> Release Note and Pull Request
Posted by Nicolas Malin via dev <de...@ofbiz.apache.org>.
Thanks all for your return !
I planned first ask how manage release note and second improve the
process if the preference gone to Github, but you already did it Mridul !
Thanks for that.
Nicolas
Le 17/10/2026 à 23:34, Mridul Pathak a écrit :
> Hi Nicolas,
>
> Following up on your proposal, I've added a .github/release.yml
> (OFBIZ-13696) so that GitHub can generate the release notes, grouped
> into Bug fixes, Improvements, New features and Documentation, with the
> rest under Other changes. Dependency updates are left out, both the
> Dependabot ones and the "Bump ..." PRs made by hand.
>
> GitHub can only group by PR labels, so I also added a small workflow
> that labels each PR from its title prefix (Fixed, Improved,
> Implemented, Documented, Bump), and I've already labelled all the PRs
> merged since 24.09.07. Since GitHub reads release.yml from the tag
> being released, once the 24.09.08 tag is re-cut, "Generate release
> notes" on the draft release should pick it up directly.
>
> Could you give it a try when you regenerate the 24.09.08 notes?
>
> Thanks,
> Mridul Pathak
>
> On Sat, Oct 17, 2026 at 11:41 PM Mridul Pathak
> <mr...@apache.org> wrote:
>
> Hi Nicolas,
>
> +1 for switching to the GitHub-generated release notes, as you did
> in your draft.
>
> Thanks,
> Mridul Pathak
>
> On Fri, Oct 16, 2026 at 6:18 PM Nicolas Malin via dev
> <de...@ofbiz.apache.org> wrote:
>
> Hello,
>
> I current work to prepare the publication of the
> release24.09.08 on our
> website (ofbiz.apache.org <http://ofbiz.apache.org>) to be
> ready when the process release will be
> ok and I'm in front of the situation to build the release note
> with the
> new commit process.
>
> At this time we build the release note from jira [1] :
>
> > Announcing the Release
> >...
> >Create an html page with the release notes (generated by Jira)
> > In Jira, mark the version as "released" and
> create a new
> version for the next release
> > Add the information about the release to the
> release
> history page: http://www.apache.org/dist/ofbiz/
> <http://www.apache.org/dist/ofbiz/>
>
> Like this we obtains the following page [2].
> Now If we follow this process, all Github Pull Request without
> jira
> issue would not be present on the release note. By the way, I
> checked
> how with github we can create the release not [3] and tried a
> draft [4]
> (like Jacopo for the 24.09.07).
>
> After that,I would tend to favor to use the release note
> generate by
> Github without Bump commit. I realized a try on my ofbiz-site
> repo [5] [6].
> Do you have any other idea/proposal ?
>
> At this end, I'll update our release process on our wiki once
> everything
> is clear
>
> Nicolas
>
> [1]
> https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
> [2] https://ofbiz.apache.org/release-notes/24.09.07.html
> [3]
> https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
> [4]
> https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
> [5]
> https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
> [6]
> https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
>
>
Re: Release process -> Release Note and Pull Request
Posted by Mridul Pathak <mr...@apache.org>.
Hi Nicolas,
Following up on your proposal, I've added a .github/release.yml
(OFBIZ-13696) so that GitHub can generate the release notes, grouped into
Bug fixes, Improvements, New features and Documentation, with the rest
under Other changes. Dependency updates are left out, both the Dependabot
ones and the "Bump ..." PRs made by hand.
GitHub can only group by PR labels, so I also added a small workflow that
labels each PR from its title prefix (Fixed, Improved, Implemented,
Documented, Bump), and I've already labelled all the PRs merged since
24.09.07. Since GitHub reads release.yml from the tag being released, once
the 24.09.08 tag is re-cut, "Generate release notes" on the draft release
should pick it up directly.
Could you give it a try when you regenerate the 24.09.08 notes?
Thanks,
Mridul Pathak
On Sat, Oct 17, 2026 at 11:41 PM Mridul Pathak <mr...@apache.org>
wrote:
> Hi Nicolas,
>
> +1 for switching to the GitHub-generated release notes, as you did in your
> draft.
>
> Thanks,
> Mridul Pathak
>
> On Fri, Oct 16, 2026 at 6:18 PM Nicolas Malin via dev <
> dev@ofbiz.apache.org> wrote:
>
>> Hello,
>>
>> I current work to prepare the publication of the release24.09.08 on our
>> website (ofbiz.apache.org) to be ready when the process release will be
>> ok and I'm in front of the situation to build the release note with the
>> new commit process.
>>
>> At this time we build the release note from jira [1] :
>>
>> > Announcing the Release
>> >...
>> >Create an html page with the release notes (generated by Jira)
>> > In Jira, mark the version as "released" and create a new
>> version for the next release
>> > Add the information about the release to the release
>> history page: http://www.apache.org/dist/ofbiz/
>> <http://www.apache.org/dist/ofbiz/>
>>
>> Like this we obtains the following page [2].
>> Now If we follow this process, all Github Pull Request without jira
>> issue would not be present on the release note. By the way, I checked
>> how with github we can create the release not [3] and tried a draft [4]
>> (like Jacopo for the 24.09.07).
>>
>> After that,I would tend to favor to use the release note generate by
>> Github without Bump commit. I realized a try on my ofbiz-site repo [5]
>> [6].
>> Do you have any other idea/proposal ?
>>
>> At this end, I'll update our release process on our wiki once everything
>> is clear
>>
>> Nicolas
>>
>> [1]
>>
>> https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
>> [2] https://ofbiz.apache.org/release-notes/24.09.07.html
>> [3]
>>
>> https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
>> [4]
>>
>> https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
>> [5]
>>
>> https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
>> [6]
>>
>> https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
>>
>
Re: Release process -> Release Note and Pull Request
Posted by Mridul Pathak <mr...@apache.org>.
Hi Nicolas,
+1 for switching to the GitHub-generated release notes, as you did in your
draft.
Thanks,
Mridul Pathak
On Fri, Oct 16, 2026 at 6:18 PM Nicolas Malin via dev <de...@ofbiz.apache.org>
wrote:
> Hello,
>
> I current work to prepare the publication of the release24.09.08 on our
> website (ofbiz.apache.org) to be ready when the process release will be
> ok and I'm in front of the situation to build the release note with the
> new commit process.
>
> At this time we build the release note from jira [1] :
>
> > Announcing the Release
> >...
> >Create an html page with the release notes (generated by Jira)
> > In Jira, mark the version as "released" and create a new
> version for the next release
> > Add the information about the release to the release
> history page: http://www.apache.org/dist/ofbiz/
> <http://www.apache.org/dist/ofbiz/>
>
> Like this we obtains the following page [2].
> Now If we follow this process, all Github Pull Request without jira
> issue would not be present on the release note. By the way, I checked
> how with github we can create the release not [3] and tried a draft [4]
> (like Jacopo for the 24.09.07).
>
> After that,I would tend to favor to use the release note generate by
> Github without Bump commit. I realized a try on my ofbiz-site repo [5] [6].
> Do you have any other idea/proposal ?
>
> At this end, I'll update our release process on our wiki once everything
> is clear
>
> Nicolas
>
> [1]
>
> https://cwiki.apache.org/confluence/spaces/OFBIZ/pages/48203381/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-AnnouncingtheRelease
> [2] https://ofbiz.apache.org/release-notes/24.09.07.html
> [3]
>
> https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
> [4]
>
> https://github.com/apache/ofbiz-framework/releases/tag/untagged-ad4481e13a2f7d0c3c67
> [5]
>
> https://github.com/apache/ofbiz-site/compare/master...nmalin:ofbiz-site:draft-release24.09.08?expand=1
> [6]
>
> https://github.com/nmalin/ofbiz-site/blob/a5388186e5b4b14de5ee18e3048bfea7cde418d0/release-notes/24.09.08.html
>