Thank you Gary.
I have updated the draft of release notes:
https://github.com/apache/maven-site/pull/99/files
I am closing the vote now and move forward with the release.
I will use that branch as base for the release notes, we can always
amend/fix/enhance them
Enrico
Il giorno lun 2 set 2019 a
FWIW, over in Apache Commons, I take the following approach when filling in
the due-to attribute for an issue in changes.xml: I list the reporter first
(the person who created the jira or wrote an email, then each person who
participated in any way in chronological order, even if it is just making
We have the contributors in POM. See this
https://github.com/apache/maven/blob/master/pom.xml#L120
This dicussion is also personal opinions which is acceptable for thinking
of new improvements in the release processes. We can always improve them
and simplify.
Next time, I vote for production of A
Agree, +1 for a single list (see last paragraph for a note on this)
@Tibor: we dont really have a contibutor section in the pom :p. Joke apart,
it cant be used at all here because it ignores the time slice the report
requires and does not scale well in time. Jira and git are reliable and
easily sc
On Mon, 02 Sep 2019 19:59:01 +0200, Enrico Olivelli
wrote:
Any suggestion ?
I am leaning towards creating a single list of "Contributors" and a list
of
"Reporters"
I agree with Romain that we're kind of mixing the different kind of
reports, but in all cases every block of text needs to
Any suggestion ?
I am leaning towards creating a single list of "Contributors" and a list of
"Reporters"
I have to close the VOTE, I will wait to reach consensus on this release
notes stuff before closing the vote.
Enrico
Il giorno sab 31 ago 2019 alle ore 17:18 Tibor Digana <
tibordig...@apach
We have contributors listed directly in the POM
https://github.com/apache/maven/blob/master/pom.xml#L120
If we started with this great idea to list contributors in POM, we should
continue with it and this is the same privilege for future contributurs as
well. They will be listed on the Maven sites
My 2cts would be that maybe we are mixing things (all points "IMHO" but
trying to make them short):
1. Changelog: jira+github driven, must be exhaustive about changes and stay
forever with a permalink on the website
2. Release notes: some highlights from the changelog, likely user impacts
mainly a
In my opinion release notes should tell:
- new features/news and noteworthy
- user visible changes
- breaking changes
I would add a list of contributors.
The list of 'reporters' is not useful.
I see we are doing those lists in order to have a better engagement with
the community, but I am not sur
For me and many users the Release Note like this are very hard to read and
hard to find what is needed.
Many times they go to google because it's easier to search than walking
through all versions of release notes.
We do not have a cumulative documentation with a list of features and we
often poin
The goal of release notes is that they are being read.
There should be a good balance of the amount of information, preventing
people to say TLDR;
A long list of 'MNG- John Doe' doesn't provide me useful information.
The list of 'MNG- A good JIRA title' is useful and visiting the
rel
We should use authors of the issue/PR/idea.
After the release we can ask WHY (practical goals) he wanted the feature
more than how. The question for "HOW" has to be placed very early during
the review, but too late after the PR has been merged.
I expect that the reviewer developer has checked all t
Not sure if the reader of the release notes is helped with a long list of
reporters and contributers per issue.
I would expect that only a list of (unique) names is good enough.
If there is someone that deserves extra credits, I'd say it is Stefan
Oehme for diving into the code, looking for m
Hi all,
I have sent a draft of the release notes for 3.6.2
this is the PR
https://github.com/apache/maven-site/pull/99/files
Feel free to add comments or push fixes directly to the branch.
It still lacks a bit of formatting, but the content is ready
Cheers
Enrico
14 matches
Mail list logo
