olamy commented on code in PR #449:
URL: https://github.com/apache/maven-site/pull/449#discussion_r1326967875
##########
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:
just look at this
https://github.com/apache/maven-compiler-plugin/releases/tag/maven-compiler-plugin-3.11.0
each PR have an appropriate label/category so there are ordered
--
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-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
