On 3/13/24 7:05 PM, Andres Almiray wrote:
First, I’d suggest following a commit message convention. You may define your
own or follow an existing one such as
https://www.conventionalcommits.org/en/v1.0.0/
+1
Next, use a tool that can read, parse, and format commit messages. You’ll find
Yes,
I meant links like these (sometimes getting into announce mail by mistake)
https://issues.apache.org/jira/projects/MNG/versions/12354062
are not public. But yes, no account needed if "just reading".
T
On Thu, Mar 14, 2024 at 9:38 AM sebb wrote:
> On Thu, 14 Mar 2024 at 08:18, Tamás
On Thu, 14 Mar 2024 at 08:18, Tamás Cservenák wrote:
>
> Howdy,
>
> What I usually do is copy-paste JIRA release notes to GH release notes:
> https://github.com/apache/maven-gpg-plugin/releases/tag/maven-gpg-plugin-3.2.0
>
> As this contains links to issues, but our JIRA does require account, so
Howdy,
What I usually do is copy-paste JIRA release notes to GH release notes:
https://github.com/apache/maven-gpg-plugin/releases/tag/maven-gpg-plugin-3.2.0
As this contains links to issues, but our JIRA does require account, so for
people "just looking around" is not simple to collect them,
Hi,
> On 13. Mar 2024, at 23:58, Slawomir Jaranowski wrote:
>
> It looks as most usable will be to manage release notes also in GitHub at
> least as link to jira public url for release notes.
> Yes I know we don't have (or have old one like maven-changes-plugin)
> perfect tools to help with
What's wrong with using a changes.xml and the plug in? You have full
control.
Gary
On Wed, Mar 13, 2024, 7:25 PM Elliotte Rusty Harold
wrote:
> On Wed, Mar 13, 2024 at 7:07 PM Andres Almiray wrote:
> >
> > First, I’d suggest following a commit message convention. You may define
> your own or
On Wed, Mar 13, 2024 at 7:07 PM Andres Almiray wrote:
>
> First, I’d suggest following a commit message convention. You may define your
> own or follow an existing one such as
> https://www.conventionalcommits.org/en/v1.0.0/
>
Please don't. I've seen this on too many projects, and it's a huge
First, I’d suggest following a commit message convention. You may define your
own or follow an existing one such as
https://www.conventionalcommits.org/en/v1.0.0/
Next, use a tool that can read, parse, and format commit messages. You’ll find
plenty of options out there. I can pitch
Hi,
Today's facts:
- We manage our issues in jira and all officala release notes are also in
jira.
- We sent an email in text format to announce mailing list.
- In project documentation we don't have a release notes
But as we see in:
