This is an automated email from the ASF dual-hosted git repository.
jaikiran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant.git
The following commit(s) were added to refs/heads/master by this push:
new 146baefac remove duplicated information from release instructions
146baefac is described below
commit 146baefac2d0d1e12fe86ee5215317a4bcb1ff9e
Author: Jaikiran Pai <jaiki...@apache.org>
AuthorDate: Sun Sep 1 18:29:57 2024 +0530
remove duplicated information from release instructions
---
ReleaseInstructions | 33 ---------------------------------
1 file changed, 33 deletions(-)
diff --git a/ReleaseInstructions b/ReleaseInstructions
index 2739726ba..a614a47a5 100644
--- a/ReleaseInstructions
+++ b/ReleaseInstructions
@@ -376,39 +376,6 @@ https://www.apache.org/dev/#releases
https://commons.apache.org/releases/index.html
https://wiki.apache.org/commons/SigningReleases
-Files containing version information
-------------------------------------
-
- * manual/cover.html
- * manual/credits.html
- * build.xml properties : project.version,manifest-version,pom.version
- * POM files under src/etc/poms and subdirectories
- * ivy.xml in release subdirectory
- * WHATSNEW
- * src/etc/testcases/taskdefs/conditions/antversion.xml
- * snap/snapcraft.yaml
-
-cover.html, credits.html, POM files, antversion.xml should be
-adjusted for the [newversion] right after the build and tagging
-of the release
-
-build.xml
----------
-
- right before a release :
-
- the project.version gets bumped to the exact release
- number, for instance 1.9.5
-
- right after a release :
-
- project.version property in build.xml gets bumped to
- [newversion]alpha, for example 1.9.6alpha
-
- manifest-version gets bumped to the exact next release number
- for example 1.9.6
-
- pom.version gets bumped to [newversion]-SNAPSHOT
