[GitHub] [maven-site] hgschmie commented on a diff in pull request #449: Improvements to release procedure

["hgschmie (via GitHub)" <gi...@apache.org>]

hgschmie commented on code in PR #449:
URL: https://github.com/apache/maven-site/pull/449#discussion_r1326591031


##########
content/apt/developers/release/maven-project-release-procedure.apt:
##########
@@ -60,6 +62,38 @@ Performing a Maven Project Release
   If the item you are planning to release is not using the most recent version of its parent
   (see {{{../../pom/}parent POMs}} index), consider taking this opportunity to update to it.
 
+* Consider updating the project dependencies
+
+  Generally it is a good that project use tha latest available versions of used dependencies.
+
+* Prepare release notes
+
+ * check all commits since latest release, all mentioned issue should be connected with release notes
+
+ * all issues should be fixed and <<CLOSED>>
+
+ * all issues should be <<assigned>> to responsible person, which fixed or merged fix

Review Comment:
   change the order? assign first, then close? 



##########
content/apt/developers/release/maven-project-release-procedure.apt:
##########
@@ -60,6 +62,38 @@ Performing a Maven Project Release
   If the item you are planning to release is not using the most recent version of its parent
   (see {{{../../pom/}parent POMs}} index), consider taking this opportunity to update to it.
 
+* Consider updating the project dependencies
+
+  Generally it is a good that project use tha latest available versions of used dependencies.
+
+* Prepare release notes
+
+ * check all commits since latest release, all mentioned issue should be connected with release notes
+
+ * all issues should be fixed and <<CLOSED>>
+
+ * all issues should be <<assigned>> to responsible person, which fixed or merged fix
+
+ * check existing issues with <<Blocker>> priority, consider to fix it or change priority if reasonable
+
+ []
+
+** Check release note at GitHub
+
+  If a component has a history of release notes at <<GitHub>>, we should to continue maintain it in order to avoid user confusing.
+
+  We can maintain release notes at <<GitHub>>, by one of:
+
+  * use release-drafter to help prepare release notes - in such case all PRs should a proper label

Review Comment:
   example?



-- 
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