You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by ti...@apache.org on 2022/05/12 10:07:41 UTC
[db-jdo] branch 3.2.1 created (now 96a16dd9)
This is an automated email from the ASF dual-hosted git repository.
tilmannz pushed a change to branch 3.2.1
in repository https://gitbox.apache.org/repos/asf/db-jdo.git
at 96a16dd9 Release preparations
This branch includes the following new commits:
new 96a16dd9 Release preparations
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.
[db-jdo] 01/01: Release preparations
Posted by ti...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tilmannz pushed a commit to branch 3.2.1
in repository https://gitbox.apache.org/repos/asf/db-jdo.git
commit 96a16dd92e24a84626d118c1f72ec06164619070
Author: Tilmann <zo...@gmx.de>
AuthorDate: Thu May 12 12:07:33 2022 +0200
Release preparations
---
HowToReleaseJDO.md | 41 ++++++++++++++++-------------------------
parent-pom/pom.xml | 7 +++++++
tck/RunRules.md | 4 ++--
3 files changed, 25 insertions(+), 27 deletions(-)
diff --git a/HowToReleaseJDO.md b/HowToReleaseJDO.md
index fa000553..144f91df 100644
--- a/HowToReleaseJDO.md
+++ b/HowToReleaseJDO.md
@@ -107,29 +107,20 @@ Detailed process steps
git checkout -b 3.2
git push -u origin 3.2
-3. In the release branch, update version numbers in the following files in
- preparation for the next release:
-
- * `tck/README.md`
- Update version number and date
-
-4. If needed, update the dependency to the RI, DataNucleus, in the tck
+3. If needed, update the dependency to the RI, DataNucleus, in the tck
`pom.xml`.
-5. If needed, apply patches from the main branch to the release branch.
-
-6. Update version numbers where necessary in projects to be released,
- if these changes haven't been made previously. Updating `pom.xml`
- files is not necessary at this point. Check the following files:
- * `README.md`
- File names and version references in the Overview section (for a
- major release only.)
+4. If needed, apply patches from the main branch to the release branch.
- * `tck/RunRules.md`
- Update version number
+5. Update version numbers where necessary in projects to be released,
+ if these changes haven't been made previously (some changes are for majopr releases only).
+ Updating `pom.xml` files is not necessary at this point. Check the following files:
+ * `README.md`
+ * `tck/RunRules.md`: Update version number and date
-7. Check the `<scm>` settings in the parent `pom.xml` file in the new branch. Note that and
- that the maven release plugin tends to remove the section. It should look as follows:
+6. Check the `<scm>` settings in the parent `pom.xml` file in the new branch. Note that and
+ that the maven release plugin tends to remove the section. It should be between
+ `<mailingLists>` and `<properties>`, and look as follows:
<scm child.scm.connection.inherit.append.path="false" child.scm.developerConnection.inherit.append.path="false"
child.scm.url.inherit.append.path="false">
@@ -138,20 +129,20 @@ Detailed process steps
<url>https://gitbox.apache.org/repos/asf?p=db-jdo.git</url>
</scm>
-8. Follow the instructions at [Publishing Maven
+7. Follow the instructions at [Publishing Maven
Artifacts](https://infra.apache.org/publishing-maven-artifacts.html)
to set up your development environment.
-9. Copy the JNDI implementation jars (`providerutil.jar` and
+8. Copy the JNDI implementation jars (`providerutil.jar` and
`fscontext.jar`) to the branch `lib/ext` directory. This is needed to
test the tck before distributing it.
**Do not check these in into the repository**
-10. Make sure the TCK passes
+9. Make sure the TCK passes
- mvn clean install
+ mvn clean install
-11. Build the distribution with the following command:
+10. Build the distribution with the following command:
mvn clean install -Papache-release -Djdo.tck.doRunTCK=false -Djdo.tck.doInstallSchema=false -Djdo.tck.doEnhance=false
@@ -160,7 +151,7 @@ Detailed process steps
to create the `<artifact>.asc` GPG signatures.
This happens multiple times.
-12. Run [Apache Rat](http://creadur.apache.org/rat) on the release
+11. Run [Apache Rat](http://creadur.apache.org/rat) on the release
artifacts to verify the results of the build.
Download Apache Rat from https://creadur.apache.org/rat/download_rat.cgi
diff --git a/parent-pom/pom.xml b/parent-pom/pom.xml
index c7d81535..4785ed85 100644
--- a/parent-pom/pom.xml
+++ b/parent-pom/pom.xml
@@ -154,6 +154,13 @@
</mailingList>
</mailingLists>
+ <scm child.scm.connection.inherit.append.path="false" child.scm.developerConnection.inherit.append.path="false"
+ child.scm.url.inherit.append.path="false">
+ <connection>scm:git:https://gitbox.apache.org/repos/asf/db-jdo.git</connection>
+ <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/db-jdo.git</developerConnection>
+ <url>https://gitbox.apache.org/repos/asf?p=db-jdo.git</url>
+ </scm>
+
<properties>
<project.build.outputTimestamp>1</project.build.outputTimestamp>
</properties>
diff --git a/tck/RunRules.md b/tck/RunRules.md
index 2c59a658..a1018bf4 100644
--- a/tck/RunRules.md
+++ b/tck/RunRules.md
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-Running the JDO 3.2 Technology Compatibility Kit
+Running the JDO 3.2.1 Technology Compatibility Kit
================================================
- [Overview](#overview)
@@ -27,7 +27,7 @@ Running the JDO 3.2 Technology Compatibility Kit
- [First Level TCK Appeals Process](#firstlevel)
- [Prerequisites](#prerequisites)
-1-November-2021
+12-May-2022
<span id="overview"></span>