If we omit tooling, I'd like to ask for volunteers presenting this initial version for 2.1.1 and 2.1.2 as a PR. It is hard for me to decide which commits to collapse into one common change description and which to keep as separate changes. :-) -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Sent: Donnerstag, 11. Oktober 2018 06:45
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Who needs this WIKI page? +1 for maintaining the changelog in the repo. IIRC we already discussed that before. But I don't think that we need any tooling for that. If we have some initial version this file, we can simply add items as part of our pull requests. Proposal: Let's stick with the Github best practice and rename the page to "CHANGELOG.md" and keep it in the repository's root folder. We even could use this tool https://github.com/github-changelog-generator/github-changelog-generator. -Markus +1 from me too for textual changelog. This is really good for a quick overview. After that the changelog can link to the GitHub diffs or milestone for more info.
On Tuesday, October 9, 2018, Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote: I agree that a classic textual changelog is useful. Of course GitHub also provides some information if you filter by milestone, but if we have many pull requests bundling changes together (for back porting to some branch for example), it is much harder to find out what the actual API changes were. Yes, the diff isn’t that useful. I will reformat it into more a changelog. I find it useful and don’t see the benefit of eagerly remove it (especially since it is linked in the original approval). I do not see a benefit from the summary either, as this is simply a non-comprehensive list, while Github already provides a comprehensive list with the Milestones feature. I actually like the "Summary of changes" section, as it is effectively a changelog. But I agree that we don't need the diff. I don't see the actual use, as one can recreate it from scratch using "git diff 2.1.1 2.1.2" at any time. So do we need to keep that page or can we discard it? I’d rather keep it for our records. Perhaps we should create one for 2.1.2, may be useful after some time. I created that wiki during the 2.1.1 approval process because they requested a detailed list of changes. Based on what you said, we may not need this for 2.1.2. what is this WIKI page for? Who needs that? Do I have to provide a similar one for 2.1.2?
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
-- _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
-- |
