You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/07/23 23:54:32 UTC

[GitHub] [maven-doxia] olamy commented on pull request #97: add release drafter configuration

olamy commented on PR #97:
URL: https://github.com/apache/maven-doxia/pull/97#issuecomment-1193209292

   > -0 IMHO, doing this for ASF project is wrong as:
   > 
   > * issues and release notes are in JIRA, JIRA is source of truth
   > * release drafter just adds another MANUAL step in already overly manual release process
   > * unsure about the quality of release notes (see Plexus containers 2.1.1 release notes done by drafter: contains TWO items, while things like QDox are not even mentioned)
   
   please provide a link as I'm not quite sure what are you talking about with plexus-containers? If you mean https://github.com/codehaus-plexus/plexus-containers. As far I can release-drafter is not used.
   By the way release-drafter generate changelog entries only from PRs merge after the last release of a repository.
   So it means:
   - if no manual release has been created with the last tag before using release-drafter the content can be confusing
   - changelog entries are generated only from PRs. So if nothing is generated for direct push to `master` branch, I guess if people push directly to `master` it probably means people thinks it's not important enough to reviewed or to be checked by some CI builds.
   
   I just wanted to improve user experience as when looking at https://maven.apache.org/doxia/ it's not really obvious to find some changelog content for a user. 
   Anyway I'm closing it.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org