Re: Please test staged JDO 3.2 release (RC5)

[Bouschen, Michael]

Hi Tilman,

I downloaded jdo-3.2-RC5-source-release.zip. I could successfully compile 
everything and ran the tck.

It looks good.

Regards Michael


Dear all,

I just staged JDO 3.2 RC5. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1005/

Changes:
- Updated dependencies to latest 5.* versions of datanucleus modules
- Removed spec PDFs
- ReleaseHowTo.md updated

Note:
In this release all files are still delivered with a .sha1 and .md5
file. This is due to a technical problem which is tracked here:
https://issues.apache.org/jira/browse/INFRA-22540
This is also the reason why RC3 failed and was no put up for a vote.

Best,
Tilmann




On 21/11/2021 18:35, Tilmann wrote:
Dear all,

I just staged JDO 3.2 RC4. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1004/

Changes:
- the "source-release" archives are now signed with SHA512 in addition
to md5/sha1
- ReleaseHowTo.md updated

Note:
In this release all files are still delivered with a .sha1 and .md5
file. This is due to a technical problem which is tracked here:
https://issues.apache.org/jira/browse/INFRA-22540
This is also the reason why RC3 failed and was no put up for a vote.

Best,
Tilmann


On 08/11/2021 23:20, Tilmann Zäschke wrote:
Dear all,

I just staged JDO 3.2 RC2. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1002

Changes:
- archives are now available as .zip and as  .tar.gz
- the "source-release" archives are now signed with SHA512
- The pom now has the "timestamp" property
- Some updates on the release instructions

Note:
- The API is still signed with sha1 only. I believe this is in line with
the
  requirement of Nexus which does not seem to support SHA256 or SHA512.
- The parent .pom has its  section removed. It gets removed by the
  release plugin, not sure whether this is a feature or how it can be
avoided.
  I will add the section again after the release.

Kind regards,
Tilmann


--
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-33
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de
Web:   www.akquinet.de

Geschäftsführung: Martin Weber, Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[Facebook]  
[XING]  
[LinkedIn]  
[Twitter]

Re: Please test staged JDO 3.2 release

[Michael Bouschen]

Hi Tilmann,

thanks for staging the rc1 JDO release, it looks good.

I downloaded jdo-3.2-RC1-source-release.zip, unpacked it, copied 
fscontext.jar and providerutil.jar to lib/ext and called mvn clean 
install. This compiled everything and ran the tck successfully.


Regards Michael


Dear all,

We are nearing the final stages of releasing JDO.3.2.

I just staged the maven artifacts for JDO 3.2 RC1. Please have a look
and report any problem.
They are available here:
https://repository.apache.org/content/repositories/orgapachejdo-1001/

Side note:
As per the instructions, the artifacts have not been released, i.e. they
are not available on the public repositories (maven central etc). I
looks like this had been handled differently for 3.1-RC1, which was
apparently released to those repositories.

Kind regards,
Til