Recommended Practice During Release?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system, release
Research direction
Start by reviewing how maven-changes-plugin handles changes.xml and how maven-release-plugin:prepare creates release and development-version commits. Determine whether the requested release-entry closing, date update, and reopening fit this plugin's scope or require coordination with the release plugin. Done means a documented, agreed design and implementation path for automating those changes.
Written by the indexing model from the issue text.
Description
New feature, improvement proposal
I am using changes.xml file in my project. Developer writes the entry
himself and it is expected to be part of the commit.
Is this recommended practice or is it more common to extract Change Log
from Git or from Jira tickets?
I would like to combine the usage of changes.xml with a release:
when maven-release-plugin:prepare creates the release commits, I would
like it to automatically close the corresponding release entry in
changes.xml and change the release date to the current date, if not
already. And after this, before committing the new development
(-SNAPSHOT) version commit, to open the corresponding release entry in
changes.xml file.
Would it make sense to add this kind of functionality to maven-changes-plugin?
- Dominant language
- Java
- Stars
- 15
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/maven-changes-plugin
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/maven-changes-plugin#650 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#633 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
apache/maven-changes-plugin#619 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
apache/maven-changes-plugin#608 ·
-
NullPointerException: Cannot invoke "java.lang.CharSequence.toString()" because "target" is null Openbug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#130 · 1 comment ·
All issues in apache/maven-changes-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100