Author: smartini
Date: Fri Dec 8 11:44:34 2023
New Revision: 1914458
URL: http://svn.apache.org/viewvc?rev=1914458&view=rev
Log:
updated doc and sample script
Modified:
pivot/infra/CREATE_RELEASE_WORKFLOW
pivot/infra/bin/setup-environment-sample.sh
Modified: pivot/infra/CREATE_RELEASE_WORKFLOW
URL:
http://svn.apache.org/viewvc/pivot/infra/CREATE_RELEASE_WORKFLOW?rev=1914458&r1=1914457&r2=1914458&view=diff
==============================================================================
--- pivot/infra/CREATE_RELEASE_WORKFLOW (original)
+++ pivot/infra/CREATE_RELEASE_WORKFLOW Fri Dec 8 11:44:34 2023
@@ -18,6 +18,7 @@ Memory and disk space required:
- 1 GB of free disk space for downloaded files and temp and build artifacts
+
Required steps:
1 - Download all Pivot files from Subversion, BUT using https, with the
following command:
@@ -29,20 +30,22 @@ so now under the current folder you have
2 - Setup environment
The Release process uses the usual pivot builds to generate binary artifacts,
so it's better to update all required tools before proceed,
-for example at the moment the latest for Java 6 is JDK 6 Update 45, for Java 7
is JDK 7 Update 80,
-and for Java 8 is JDK 8 Update 131.
+for example at the moment the latest for Java 8 is JDK 8 Update 392, for Java
11 is JDK 11 Update 21.
+
+To buil full release, the env var PIVOT_RELEASE has to be defined with the
right value,
+so define a shell variable for this, like:
+export PIVOT_RELEASE=<release-number>
+Of course <release-number> in this document has to be changed with the real
release version,
+for example currently it's 2.1.0 in trunk, and 2.0.5 in branches/2.0.x .
-Some environment variables are needed, so you need to define them accordingly
to your environment.
+Some environment variables are needed for build/test tasks, so you need to
define
+them accordingly to your environment.
As a sample you can look at (but please do NOT commit changes to it):
infra/bin/setup-environment-sample.sh
-Note that currently you need to copy its contents and paste in a terminal, or
in your profile file.
-
-Of course <release-number> in this document has to be changed with the real
release version,
-for example currently it's 2.1.0 in trunk, and 2.0.5 in branches/2.0.x .
-A good trick could be even to define a shell variable for this, like:
-export PIVOT_RELEASE=<release-number>
-and then use it.
+Note that currently you need to copy its contents and paste in a terminal, or
in your profile file,
+or run it but in a way to source its env vars in current shell, like:
+. ../infra/bin/setup-environment-sample.sh
Note that until now, this procedure has been used only to build releases from
the trunk,
so to build from a branch (for example branches/2.0.x) probably only relative
path should be fixed a little
@@ -51,7 +54,9 @@ Anyway, it's better to keep this procedu
-Generated artifacts will be digitally signed by PGP / GPG, so the Release
Manager MUST have a valid PGP / GPG sign (on its apache.org mail address), and
must be published to some public key server (for example the MIT Key server),
and that sign must be appended at the and of the KEYS file (under the trunk)
and committed.
+Generated artifacts will be digitally signed by PGP / GPG, so the Release
Manager MUST have a valid PGP / GPG sign
+(on its apache.org mail address), and must be published to some public key
server (for example the MIT Key server),
+and that sign must be appended at the and of the KEYS file (under the trunk)
and committed.
3 - Keep all files in synch with the repository
@@ -164,7 +169,7 @@ From the release folder, for example run
scp ./*
smart...@people.apache.org:~/public_html/pivot-<release-number>_release/
currently it contains approx. 60 MB of files.
-Than, verify with a Web Browser that all stuff has been copied and published,
for example from here:
+Then, verify with a Web Browser that all stuff has been copied and published,
for example from here:
http://people.apache.org/~smartini/
Important: the release content is really needed, but the maven content could
be copied there only for convenience, so someone with access to a real maven
Repository could publish them ... BUT only after the release has been voted and
published.
@@ -176,3 +181,5 @@ with a minimum duration time of 3 days o
but if possible with a week-end inside so people have more time to test all.
+----
+
Modified: pivot/infra/bin/setup-environment-sample.sh
URL:
http://svn.apache.org/viewvc/pivot/infra/bin/setup-environment-sample.sh?rev=1914458&r1=1914457&r2=1914458&view=diff
==============================================================================
--- pivot/infra/bin/setup-environment-sample.sh (original)
+++ pivot/infra/bin/setup-environment-sample.sh Fri Dec 8 11:44:34 2023
@@ -23,20 +23,18 @@
export TEMP_DIR=/tmp
export OPT=/opt
-# export ANT_HOME=$OPT/apache-ant-1.8.4
-export ANT_HOME=$OPT/apache-ant-1.9.9
-# export ANT_HOME=$OPT/apache-ant-1.10.1
-export JAVA_HOME=$OPT/jdk1.6.0_45
-# export JAVA_HOME=$OPT/jdk1.7.0_80
+# export ANT_HOME=$OPT/apache-ant-1.10.12
+export ANT_HOME=$OPT/apache-ant-1.10.14
# export JAVA_HOME=$OPT/jdk1.8.0_131
-export MAVEN_HOME=$OPT/apache-maven-3.3.9
-# export MAVEN_HOME=$OPT/apache-maven-3.5.0
+export JAVA_HOME=$OPT/jdk-11
+# export MAVEN_HOME=$OPT/apache-maven-3.6.3
+export MAVEN_HOME=$OPT/apache-maven-3.9.5
export JAVALIB_DIR=$OPT/javalib
-export JUNIT_LIB=$JAVALIB_DIR/junit-4.12.jar
+export
JUNIT_LIB=$JAVALIB_DIR/junit-4.13.2.jar:$JAVALIB_DIR/hamcrest-core-1.3.jar
export MAVEN_ANT_TASKS_LIB=$JAVALIB_DIR/maven-ant-tasks-2.1.3.jar
-export RAT_LIB=$JAVALIB_DIR/apache-rat-0.11.jar
+export RAT_LIB=$JAVALIB_DIR/apache-rat-0.13.jar
export GPG_KEY_EMAIL=smart...@apache.org
