You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by re...@apache.org on 2026/08/18 12:51:12 UTC

(sling-site) branch reschke-patch-2 created (now b03f3b3db)

This is an automated email from the ASF dual-hosted git repository.

reschke pushed a change to branch reschke-patch-2
in repository https://gitbox.apache.org/repos/asf/sling-site.git


      at b03f3b3db Clarify pom.xml comparison in release management

This branch includes the following new commits:

     new b03f3b3db Clarify pom.xml comparison in release management

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



(sling-site) 01/01: Clarify pom.xml comparison in release management

Posted by re...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

reschke pushed a commit to branch reschke-patch-2
in repository https://gitbox.apache.org/repos/asf/sling-site.git

commit b03f3b3db61f609f082a3636c97efd67a0cf9fad
Author: Julian Reschke <re...@apache.org>
AuthorDate: Tue Aug 18 14:51:05 2026 +0200

    Clarify pom.xml comparison in release management
    
    Updated release management instructions to include project.build.outputTimestamp in the comparison of pom.xml files.
---
 src/main/jbake/content/documentation/development/release-management.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index a78a2f9bc..2ad97ed6f 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -152,7 +152,7 @@ First prepare your POMs for release:
 
         $ mvn release:prepare -DdryRun=true
 
-    Compare the original `pom.xml` with the one called `pom.xml.tag` to see if the license or any other info has been removed. This has been known to happen if the starting `<project>` tag is not on a single line. The only things that should be different between these files are the `<version>` and `<scm>` elements. If there are any other changes, you must fix the original `pom.xml` file and commit before proceeding with the release.
+    Compare the original `pom.xml` with the one called `pom.xml.tag` to see if the license or any other info has been removed. This has been known to happen if the starting `<project>` tag is not on a single line. The only things that should be different between these files are the `<version>`, `<project.build.outputTimestamp>` and `<scm>` elements. If there are any other changes, you must fix the original `pom.xml` file and commit before proceeding with the release.
 
 1. Publish a snapshot