sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From desruisse...@apache.org
Subject svn commit: r1867020 - in /sis/site/trunk/content: downloads.mdtext mail-lists.mdtext release-management-setup.mdtext release-management.mdtext
Date Mon, 16 Sep 2019 16:44:55 GMT
Author: desruisseaux
Date: Mon Sep 16 16:44:54 2019
New Revision: 1867020

URL: http://svn.apache.org/viewvc?rev=1867020&view=rev
Log:
Remove some obsolete material from release management page.

Modified:
    sis/site/trunk/content/downloads.mdtext
    sis/site/trunk/content/mail-lists.mdtext
    sis/site/trunk/content/release-management-setup.mdtext
    sis/site/trunk/content/release-management.mdtext

Modified: sis/site/trunk/content/downloads.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/downloads.mdtext?rev=1867020&r1=1867019&r2=1867020&view=diff
==============================================================================
--- sis/site/trunk/content/downloads.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/downloads.mdtext [UTF-8] Mon Sep 16 16:44:54 2019
@@ -47,7 +47,7 @@ Verify signatures    {#release-gpg}
 
 All downloads can be verified using the Apache SIS code signing [KEYS][keys].
 The PGP (_Pretty Good Privacy_) signatures can be verified using any OpenPGP implementation,
for example GPG (_GNU Privacy Guard_).
-First download the `[KEYS][keys]` file as well as the `.asc` signature files for the relevant
release packages.
+First download the [KEYS][keys] file and the `.asc` signature files for the relevant release
packages.
 Make sure you get these files from the main distribution directory, rather than from a mirror.
 Then verify the signatures using the following:
 
@@ -77,7 +77,7 @@ Download as a Maven dependency    {#mave
 An easy approach to integrate Apache SIS into a Java project uses the [Apache Maven][maven]
 dependency management tool to automatically obtain the required Java Archives (JAR) files
from the network.
 Below are examples of declarations in a `pom.xml` file for building a project with a SIS
core module.
-If running on Java 11 or higher, _one_ of the two next dependencies is also required:
+If running on Java 11 or higher, at least one of the two next dependencies is also required:
 
     :::xml
     <properties>

Modified: sis/site/trunk/content/mail-lists.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/mail-lists.mdtext?rev=1867020&r1=1867019&r2=1867020&view=diff
==============================================================================
--- sis/site/trunk/content/mail-lists.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/mail-lists.mdtext [UTF-8] Mon Sep 16 16:44:54 2019
@@ -45,8 +45,8 @@ This is where users can ask questions ab
   - Post (after subscription): [user@sis.apache.org][usr-post]
   - Unsubscribe: [user-unsubscribe@sis.apache.org][usr-unsub]
   - Archives:
-    - [Apache][usr-arch]
     - [Pony mail][usr-pony-arch]
+    - [Apache][usr-arch]
 
 
 
@@ -59,8 +59,8 @@ This is where the community hangs out an
   - Post (after subscription): [dev@sis.apache.org][dev-post]
   - Unsubscribe: [dev-unsubscribe@sis.apache.org][dev-unsub]
   - Archives:
-    - [Apache][dev-arch]
     - [Pony mail][dev-pony-arch]
+    - [Apache][dev-arch]
 
 
 
@@ -73,8 +73,8 @@ any changes to the sis code and document
   - Subscribe: [commits-subscribe@sis.apache.org][com-sub]
   - Unsubscribe: [commmits-unsubscribe@sis.apache.org][com-unsub]
   - Archives:
-    - [Apache][com-arch]
     - [Pony mail][com-pony-arch]
+    - [Apache][com-arch]
 
 
   [geo-sub]:   mailto:geospatial-subscribe@apache.org

Modified: sis/site/trunk/content/release-management-setup.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/release-management-setup.mdtext?rev=1867020&r1=1867019&r2=1867020&view=diff
==============================================================================
--- sis/site/trunk/content/release-management-setup.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/release-management-setup.mdtext [UTF-8] Mon Sep 16 16:44:54 2019
@@ -35,8 +35,6 @@ However in the later case, all relative
     :::text
     <any root directory for SIS>
     ├─ master
-    ├─ branches
-    ├─ tags
     ├─ non-free
     │  ├─ sis-epsg
     │  └─ sis-embedded-data
@@ -53,8 +51,6 @@ Create the above directory structure as
     svn checkout https://svn.apache.org/repos/asf/sis/release-test
     svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site
     svn checkout https://dist.apache.org/repos/dist/dev/sis distribution
-    mkdir branches
-    mkdir tags
 
 
 

Modified: sis/site/trunk/content/release-management.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/release-management.mdtext?rev=1867020&r1=1867019&r2=1867020&view=diff
==============================================================================
--- sis/site/trunk/content/release-management.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/release-management.mdtext [UTF-8] Mon Sep 16 16:44:54 2019
@@ -32,7 +32,7 @@ Configure    {#configure}
 Before to perform a release, make sure that the following conditions hold:
 
   * Commands will be executed in a Unix shell.
-  * Subversion, GNU GPG, ZIP, Maven, Ant, Java and the Java compiler are available on the
path.
+  * Git, Subversion, GNU GPG, ZIP, Maven, Ant, Java and the Java compiler are available on
the path.
   * The [release management setup](release-management-setup.html) steps have been executed
once.
 
 For all instructions in this page, `$OLD_VERSION` and `$NEW_VERSION` stand for the version
@@ -44,16 +44,11 @@ the current release attempt. Those versi
     export NEW_VERSION=1.0
     export RELEASE_CANDIDATE=1
     export SIGNING_KEY=<your key ID>
-    export BOOTCLASSPATH=<path to the rt.jar file of a JDK7 installation>
+    unset PATH_TO_FX
 
 The key ID value is an hexadecimal numbers with 8 digits (may be the last 8 digits of a 40
digits number).
 It can be found be executing `gpg --list-keys`.
 
-The boot class path value is highly system-dependent. Some examples are:
-
-  * `/usr/lib/jvm/java-7/jre/lib/rt.jar` on some Linux distributions (replace `java-7` by
the actual directory name).
-  * `/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/rt.jar` on MacOS.
-
 Starts the GPG agent if not already done.
 This is for avoiding to be prompted many time for the passphrase in every modules to be built
by Maven.
 
@@ -72,12 +67,6 @@ in this page shall be adjusted according
     :::text
     <any root directory for SIS>
     ├─ master
-    ├─ branches
-    │  └─ $NEW_VERSION
-    ├─ tags
-    │  └─ $NEW_VERSION
-    │     └─ target
-    │        └─ distributions
     ├─ non-free
     │  └─ sis-epsg
     ├─ distribution
@@ -89,20 +78,8 @@ in this page shall be adjusted according
 
 
 
-Java versions    {#java-version}
---------------------------------
-
-While we need a JDK7 installation for the `bootclasspath` option, we do not recommend to
use it for generating
-the binaries since JDK7 has reached its end of public updates (but not the end of commercial
support).
-We recommend to create the release with JDK8 instead (note however that JDK8 `javadoc` tool
seems to have a bug that prevent its use with SIS).
-Make sure that the JDK installation to be used for the release has been updated recently,
since compilers may receive critical bug fixes.
-For example the `javadoc` tool of older JDK versions was known to generate HTML pages with
a vulnerability in them.
-
-
-
-
-Prepare web site and source code before branching    {#prepare-source}
-======================================================================
+Review project status before branching    {#prepare-source}
+===========================================================
 
 Before to start the release process, we need to test more extensively the master.
 The tests described below often reveal errors that were unnoticed in daily builds.
@@ -111,49 +88,35 @@ First:
 
   * Review and update the `README` and `NOTICE` files on the source code repository.
   * Review the `javac` and `javadoc` warnings reported by Jenkins and fix at least the typos.
+  * Tests the following commands:
+
+    :::bash
+    mvn clean install --define org.apache.sis.test.extensive=true
+    mvn javadoc::aggregate
 
 
 
 Prepare release notes    {#release-notes}
 -----------------------------------------
 
-We update JIRA first because doing so is sometime a reminder of uncompleted tasks in source
code.
+We update JIRA soon because doing so is sometime a reminder of uncompleted tasks in source
code.
 Update [JIRA][JIRA] tasks and prepare release notes as below:
 
   * Ensure that the _Fix Version_ in issues resolved since the last release includes this
release version correctly.
   * Ensure that all open issues are resolved or closed before proceeding further.
   * On the `site` source code repository, create a `content/release-notes/$NEW_VERSION.html`
file with all the features added.
   * Use `content/release-notes/$OLD_VERSION.html` as a template, omitting everything between
the `<body>` and `</body>` tags.
-  * The release notes can be obtained from JIRA, by clicking on the _Roadmap_ tab → the
version number → _Release notes_
+  * The release notes can be obtained from JIRA, by clicking on the _Versions_ tab → the
version number → _Release notes_
     and then configuring the release notes to display HTML format and copying it.
     A suggested approach would be to reorganize the release notes as
     _New Features_, then _Improvements_, then _Bug Fixes_, then _Tests_ and finally _Tasks_.
     The _Sub Tasks_ can be classified according the category of their parent issue.
 
-
-
-Web site    {#prepare-website}
-------------------------------
-
-Review and update the `content/DOAP.rdf` file on the `site` source code repository.
-Add a new `<release>` block for the new release with the estimated release date.
-
-Update the version numbers from the old one to `$NEW_VERSION` in the following files.
-
-  * `content/index.mdtext`
-  * `content/gdal.mdtext`
-  * `content/downloads.mdtext` (need also to update `$NEW_VERSION-SNAPSHOT` to the next snapshot
version)
-  * `content/command-line.mdtext`
-  * `content/epsg.mdtext` (be aware that the version number may sometime be behind the SIS
version number)
-
-Commit:
+Commit to staging area (not published immediately):
 
     :::bash
     svn add content/release-notes/$NEW_VERSION.html
-    svn commit --message "Prepare documentation for the $NEW_VERSION release."
-
-The new web site will be published in the [staging area](http://sis.staging.apache.org).
-It will not yet be published on `http://sis.apache.org`.
+    svn commit --message "Release notes for Apache SIS $NEW_VERSION."
 
 
 
@@ -173,8 +136,7 @@ This profile performs the following acti
 Each of those additional products may cause a failure that did not happen in normal builds.
 
     :::bash
-    cd ../master
-    mvn clean install --activate-profiles apache-release --define bootclasspath=$BOOTCLASSPATH
+    mvn clean install --activate-profiles apache-release
 
 Verify signature for all files:
 
@@ -191,7 +153,7 @@ SIS dependencies are the snapshot tested
     :::bash
     cd ../non-free
     svn update
-    mvn clean install --define bootclasspath=$BOOTCLASSPATH
+    mvn clean install
 
 Run the integration tests. Before to test,
 verify that their version numbers and their SIS dependencies are the snapshot tested in this
section.
@@ -201,7 +163,7 @@ Note that execution of those tests may b
     cd ../release-test
     svn update
     cd maven
-    mvn clean test --define bootclasspath=$BOOTCLASSPATH
+    mvn clean test
 
 
 
@@ -261,7 +223,7 @@ Validate with `git diff`, ensure that th
 then commit the changes on the branch:
 
     :::bash
-    mvn clean package --define skipTests=true --define bootclasspath=$BOOTCLASSPATH
+    mvn clean package --define skipTests=true
     git commit --message "Prepare branch for $NEW_VERSION release."
 
 
@@ -307,7 +269,7 @@ Build and test the project in the same w
 In addition to testing, execution of an `install` phase before deployment is required for
our custom `sis-build-helper` plugin.
 
     :::bash
-    mvn install --activate-profiles apache-release --define bootclasspath=$BOOTCLASSPATH
+    mvn install --activate-profiles apache-release
     find . -name "sis-*.asc" -exec gpg --verify '{}' \;
 
 Open the `pom.xml` file of all modules in the `non-free` group.
@@ -319,7 +281,7 @@ Commit and built:
     :::bash
     cd ../../non-free
     svn commit --message "Set version number and dependencies to $NEW_VERSION."
-    mvn clean install --define bootclasspath=$BOOTCLASSPATH
+    mvn clean install
 
 Open the `pom.xml` file of integration tests.
 Set its version numbers and its SIS dependencies to `$NEW_VERSION` without `-SNAPSHOT` suffix.
@@ -329,7 +291,7 @@ Commit and built (note that execution ma
     cd ../release-test
     svn commit --message "Set version number and dependencies to $NEW_VERSION."
     cd maven
-    mvn clean test --define bootclasspath=$BOOTCLASSPATH
+    mvn clean test
 
 
 
@@ -340,7 +302,7 @@ If above verifications succeeded, deploy
 
     :::bash
     chmod a-w target/distribution/*.zip
-    mvn deploy --activate-profiles apache-release --define bootclasspath=$BOOTCLASSPATH
+    mvn deploy --activate-profiles apache-release
 
 
 
@@ -391,7 +353,7 @@ Replace occurrences of `<version>$OLD_VE
 Deploy:
 
     :::bash
-    mvn deploy --activate-profiles apache-release --define bootclasspath=$BOOTCLASSPATH
+    mvn deploy --activate-profiles apache-release
 
 In Nexus:
 
@@ -600,6 +562,30 @@ to build the add-in:
 
 
 
+Prepare Web site    {#prepare-website}
+======================================
+
+Review and update the `content/DOAP.rdf` file on the `site` source code repository.
+Add a new `<release>` block for the new release with the estimated release date.
+
+Update the version numbers from the old one to `$NEW_VERSION` in the following files.
+
+  * `content/index.mdtext`
+  * `content/gdal.mdtext`
+  * `content/downloads.mdtext` (need also to update `$NEW_VERSION-SNAPSHOT` to the next snapshot
version)
+  * `content/command-line.mdtext`
+  * `content/epsg.mdtext` (be aware that the version number may sometime be behind the SIS
version number)
+
+Commit:
+
+    :::bash
+    svn commit --message "Prepare documentation for the $NEW_VERSION release."
+
+The new web site will be published in the [staging area](http://sis.staging.apache.org).
+It will not yet be published on `http://sis.apache.org`.
+
+
+
 Put the release candidate up for a vote    {#vote}
 ==================================================
 



Mime
View raw message