Skip to content

Commit

Permalink
[maven-release-plugin] prepare release plexus-archiver-4.2.2
Browse files Browse the repository at this point in the history
  • Loading branch information
@plamentotev
plamentotev committed Feb 29, 2020
1 parent 3e1af62 commit 02f0331
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions pom.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,14 @@
</parent>

<artifactId>plexus-archiver</artifactId>
<version>4.2.2-SNAPSHOT</version>
<version>4.2.2</version>
<name>Plexus Archiver Component</name>

<scm>
<connection>scm:git:git@github.com:codehaus-plexus/plexus-archiver.git</connection>
<developerConnection>scm:git:git@github.com:codehaus-plexus/plexus-archiver.git</developerConnection>
<url>http://github.com/codehaus-plexus/plexus-archiver/tree/${project.scm.tag}/</url>
<tag>master</tag>
<tag>plexus-archiver-4.2.2</tag>
</scm>
<issueManagement>
<system>jira</system>
Expand All @@ -32,7 +32,7 @@

<properties>
<javaVersion>7</javaVersion>
<project.build.outputTimestamp>2020-01-20T18:52:37Z</project.build.outputTimestamp>
<project.build.outputTimestamp>2020-02-29T18:20:48Z</project.build.outputTimestamp>
</properties>

<contributors>
Expand Down

5 comments on commit 02f0331

@vmassol
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@plamentotev Thanks for updating the RN at 4a75dbf

It seems they were not updated after the 4.2.2 release though. Would be great to add that! ;)

Thx

@plamentotev
Copy link
Member Author

@plamentotev plamentotev commented on 02f0331 Oct 3, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vmassol Looks like Plexus project is moving to GitHub releases for release notes. Any suggestions what to do with this file? /cc @olamy @rfscholte

@rfscholte
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Funny, it looks like in the days we had Jira at Codehaus, things went smoother. But all codehaus-plexus repos have the same issue. I prefer not too much extra work when releasing, but that means we all need to do our administration better in Github, assigning milestones.

@olamy
Copy link
Member

@olamy olamy commented on 02f0331 Oct 3, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you correctly add label to your pull request (see details here https://github.com/codehaus-plexus/.github/blob/master/.github/release-drafter.yml) the release draft will be nicely/smoothly generated. Just don't forget to publish it once you released the artifacts.

@plamentotev
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release drafter would work for next releases. I wonder what to do with the existing file. Leave it and give a link to GitHub release for the newer releases, or migrate the old release notes to GitHub releases (using script) and delete the file. I think the second option is better, but wanted to ask in case you have some concerns.

And while we are the topic. What do you think about migrating the JIRA issues from jira folder? For reference. And actually some of them are still open. Not sure if there will be value of keeping them open as some time has passed and maybe some are fixed.

Please sign in to comment.