Re: Minutes: JDO TCK Conference Call Thursday November 25 11 AM PST 20 CET

[Craig Russell]

Hi,

> On Nov 27, 2021, at 10:34 AM, Michael Bouschen  wrote:
> 
> Hi,
> 
> I think you propose remove the two pdf files 3.1 and 3.1-rc1 from the 
> distribution and keep them in the git repository, correct? I agree to remove 
> them from the distribution.

That's it. Since the .pdf file can be created trivially using OpenOffice it 
really doesn't need to be part of the source distribution.
> 
> I also agree creating a new rc5 with the datanucleus dependencies that Andy 
> provided.

I will still not wait for this before contacting JCP with the rc4 artifacts 
that we have already. 

Regards Craig
> 
> Regards Michael
> 
>> Hi Til,
>> 
>> Just one lil thing that I noticed.
>> 
>> The specification/OOO directory has two pdf files: 3.1 and 3.1-rc1. We 
>> should probably just remove these since it is a source release. I'll 
>> generate a 3.2.pdf for the JCP but I really think we don't need the pdf for 
>> the release.
>> 
>> Thanks,
>> Craig
>> 
>>> On Nov 27, 2021, at 9:11 AM, Tilmann  wrote:
>>> 
>>> Hi,
>>> 
>>> since we want to support JRE 1.8+ I should probably create a new RC5
>>> with the dependencies that Andy provided.
>>> 
>>> If nobody objects I will set up a new RC tomorrow.
>>> 
>>> Best,
>>> Til
>>> 
>>> 
>>> On 27/11/2021 17:05, Craig Russell wrote:
 Hi Andy,
 
 Thanks for helping us get the best possible list of DataNucleus 
 dependencies for the release.
 
 Thanks for clarifying the purpose of the api-jdo jar. I had a 
 misunderstanding of what the datanucleus-api-jdo was, having never 
 actually looked at it. I should have asked the question instead of 
 suggesting that it be removed. My bad.
 
 It will help greatly if you could also look at the release artifacts that 
 Tilmann sent a link to.
 
 Warm regards,
 Craig
 
> On Nov 27, 2021, at 5:53 AM, Andy Jefferson  wrote:
> 
>> 1. JDO 3.2 release RC4
>> The release includes DataNucleus reference in the pom: core 5.2.7;
>> rdbms 5.2.7; api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6.
>> Are these the right DataNucleus versions for the 3.2 release?
>> We probably should remove the datanucleus api-jdo and instead use the 
>> official
> 3.2 api.
> 
> If you intend JDO 3.2 to be for JRE 1.8+ then you need the LATEST in the 
> v5.x
> series
> datanucleus-core 5.2.9
> datanucleus-api-jdo 5.2.7
> datanucleus-api-jpa 5.2.8
> datanucleus-rdbms 5.2.9
> datanucleus-jdo-query 5.0.9
> 
> Removing datanucleus-api-jdo will make your life much harder since then 
> you
> will be testing DataNucleus with NO SUPPORT for the JDO API. That is the 
> DN
> API-support jar, not the API interfaces. Just like the associated 
> datanucleus-
> api-jpa jar provides SUPPORT for the JPA API.
> 
> 
> 
> Regards
> --
> Andy
> DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)
> 
> 
 Craig L Russell
 c...@apache.org
 
>> Craig L Russell
>> c...@apache.org
>> 
> 

Craig L Russell
c...@apache.org

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]

Please test staged JDO 3.2 release (RC5)

[Tilmann]

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

Re: Minutes: JDO TCK Conference Call Thursday November 25 11 AM PST 20 CET

[Michael Bouschen]

Hi,

I think you propose remove the two pdf files 3.1 and 3.1-rc1 from the 
distribution and keep them in the git repository, correct? I agree to 
remove them from the distribution.


I also agree creating a new rc5 with the datanucleus dependencies that 
Andy provided.


Regards Michael


Hi Til,

Just one lil thing that I noticed.

The specification/OOO directory has two pdf files: 3.1 and 3.1-rc1. We should 
probably just remove these since it is a source release. I'll generate a 
3.2.pdf for the JCP but I really think we don't need the pdf for the release.

Thanks,
Craig


On Nov 27, 2021, at 9:11 AM, Tilmann  wrote:

Hi,

since we want to support JRE 1.8+ I should probably create a new RC5
with the dependencies that Andy provided.

If nobody objects I will set up a new RC tomorrow.

Best,
Til


On 27/11/2021 17:05, Craig Russell wrote:

Hi Andy,

Thanks for helping us get the best possible list of DataNucleus dependencies 
for the release.

Thanks for clarifying the purpose of the api-jdo jar. I had a misunderstanding 
of what the datanucleus-api-jdo was, having never actually looked at it. I 
should have asked the question instead of suggesting that it be removed. My bad.

It will help greatly if you could also look at the release artifacts that 
Tilmann sent a link to.

Warm regards,
Craig


On Nov 27, 2021, at 5:53 AM, Andy Jefferson  wrote:


1. JDO 3.2 release RC4
The release includes DataNucleus reference in the pom: core 5.2.7;
rdbms 5.2.7; api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6.
Are these the right DataNucleus versions for the 3.2 release?
We probably should remove the datanucleus api-jdo and instead use the official

3.2 api.

If you intend JDO 3.2 to be for JRE 1.8+ then you need the LATEST in the v5.x
series
datanucleus-core 5.2.9
datanucleus-api-jdo 5.2.7
datanucleus-api-jpa 5.2.8
datanucleus-rdbms 5.2.9
datanucleus-jdo-query 5.0.9

Removing datanucleus-api-jdo will make your life much harder since then you
will be testing DataNucleus with NO SUPPORT for the JDO API. That is the DN
API-support jar, not the API interfaces. Just like the associated datanucleus-
api-jpa jar provides SUPPORT for the JPA API.



Regards
--
Andy
DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)



Craig L Russell
c...@apache.org


Craig L Russell
c...@apache.org

Re: Minutes: JDO TCK Conference Call Thursday November 25 11 AM PST 20 CET

[Craig Russell]

Hi Til,

Just one lil thing that I noticed.

The specification/OOO directory has two pdf files: 3.1 and 3.1-rc1. We should 
probably just remove these since it is a source release. I'll generate a 
3.2.pdf for the JCP but I really think we don't need the pdf for the release.

Thanks,
Craig

> On Nov 27, 2021, at 9:11 AM, Tilmann  wrote:
> 
> Hi,
> 
> since we want to support JRE 1.8+ I should probably create a new RC5
> with the dependencies that Andy provided.
> 
> If nobody objects I will set up a new RC tomorrow.
> 
> Best,
> Til
> 
> 
> On 27/11/2021 17:05, Craig Russell wrote:
>> Hi Andy,
>> 
>> Thanks for helping us get the best possible list of DataNucleus dependencies 
>> for the release.
>> 
>> Thanks for clarifying the purpose of the api-jdo jar. I had a 
>> misunderstanding of what the datanucleus-api-jdo was, having never actually 
>> looked at it. I should have asked the question instead of suggesting that it 
>> be removed. My bad.
>> 
>> It will help greatly if you could also look at the release artifacts that 
>> Tilmann sent a link to.
>> 
>> Warm regards,
>> Craig
>> 
>>> On Nov 27, 2021, at 5:53 AM, Andy Jefferson  wrote:
>>> 
 1. JDO 3.2 release RC4
 The release includes DataNucleus reference in the pom: core 5.2.7;
 rdbms 5.2.7; api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6.
 Are these the right DataNucleus versions for the 3.2 release?
 We probably should remove the datanucleus api-jdo and instead use the 
 official
>>> 3.2 api.
>>> 
>>> If you intend JDO 3.2 to be for JRE 1.8+ then you need the LATEST in the 
>>> v5.x
>>> series
>>> datanucleus-core 5.2.9
>>> datanucleus-api-jdo 5.2.7
>>> datanucleus-api-jpa 5.2.8
>>> datanucleus-rdbms 5.2.9
>>> datanucleus-jdo-query 5.0.9
>>> 
>>> Removing datanucleus-api-jdo will make your life much harder since then you
>>> will be testing DataNucleus with NO SUPPORT for the JDO API. That is the DN
>>> API-support jar, not the API interfaces. Just like the associated 
>>> datanucleus-
>>> api-jpa jar provides SUPPORT for the JPA API.
>>> 
>>> 
>>> 
>>> Regards
>>> --
>>> Andy
>>> DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)
>>> 
>>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: Minutes: JDO TCK Conference Call Thursday November 25 11 AM PST 20 CET

[Tilmann]

Hi,

since we want to support JRE 1.8+ I should probably create a new RC5
with the dependencies that Andy provided.

If nobody objects I will set up a new RC tomorrow.

Best,
Til


On 27/11/2021 17:05, Craig Russell wrote:

Hi Andy,

Thanks for helping us get the best possible list of DataNucleus dependencies 
for the release.

Thanks for clarifying the purpose of the api-jdo jar. I had a misunderstanding 
of what the datanucleus-api-jdo was, having never actually looked at it. I 
should have asked the question instead of suggesting that it be removed. My bad.

It will help greatly if you could also look at the release artifacts that 
Tilmann sent a link to.

Warm regards,
Craig


On Nov 27, 2021, at 5:53 AM, Andy Jefferson  wrote:


1. JDO 3.2 release RC4
The release includes DataNucleus reference in the pom: core 5.2.7;
rdbms 5.2.7; api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6.
Are these the right DataNucleus versions for the 3.2 release?
We probably should remove the datanucleus api-jdo and instead use the official

3.2 api.

If you intend JDO 3.2 to be for JRE 1.8+ then you need the LATEST in the v5.x
series
datanucleus-core 5.2.9
datanucleus-api-jdo 5.2.7
datanucleus-api-jpa 5.2.8
datanucleus-rdbms 5.2.9
datanucleus-jdo-query 5.0.9

Removing datanucleus-api-jdo will make your life much harder since then you
will be testing DataNucleus with NO SUPPORT for the JDO API. That is the DN
API-support jar, not the API interfaces. Just like the associated datanucleus-
api-jpa jar provides SUPPORT for the JPA API.



Regards
--
Andy
DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)



Craig L Russell
c...@apache.org

Re: Minutes: JDO TCK Conference Call Thursday November 25 11 AM PST 20 CET

[Craig Russell]

Hi Andy,

Thanks for helping us get the best possible list of DataNucleus dependencies 
for the release.

Thanks for clarifying the purpose of the api-jdo jar. I had a misunderstanding 
of what the datanucleus-api-jdo was, having never actually looked at it. I 
should have asked the question instead of suggesting that it be removed. My bad.

It will help greatly if you could also look at the release artifacts that 
Tilmann sent a link to. 

Warm regards,
Craig

> On Nov 27, 2021, at 5:53 AM, Andy Jefferson  wrote:
> 
>> 1. JDO 3.2 release RC4
>> The release includes DataNucleus reference in the pom: core 5.2.7; 
>> rdbms 5.2.7; api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6.
>> Are these the right DataNucleus versions for the 3.2 release? 
>> We probably should remove the datanucleus api-jdo and instead use the 
>> official 
> 3.2 api. 
> 
> If you intend JDO 3.2 to be for JRE 1.8+ then you need the LATEST in the v5.x 
> series
> datanucleus-core 5.2.9
> datanucleus-api-jdo 5.2.7
> datanucleus-api-jpa 5.2.8
> datanucleus-rdbms 5.2.9
> datanucleus-jdo-query 5.0.9
> 
> Removing datanucleus-api-jdo will make your life much harder since then you 
> will be testing DataNucleus with NO SUPPORT for the JDO API. That is the DN 
> API-support jar, not the API interfaces. Just like the associated datanucleus-
> api-jpa jar provides SUPPORT for the JPA API.
> 
> 
> 
> Regards
> -- 
> Andy
> DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)
> 
> 

Craig L Russell
c...@apache.org

Re: Minutes: JDO TCK Conference Call Thursday November 25 11 AM PST 20 CET

[Andy Jefferson]

> 1. JDO 3.2 release RC4
> The release includes DataNucleus reference in the pom: core 5.2.7; 
> rdbms 5.2.7; api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6.
> Are these the right DataNucleus versions for the 3.2 release? 
> We probably should remove the datanucleus api-jdo and instead use the 
> official 
3.2 api. 

If you intend JDO 3.2 to be for JRE 1.8+ then you need the LATEST in the v5.x 
series
datanucleus-core 5.2.9
datanucleus-api-jdo 5.2.7
datanucleus-api-jpa 5.2.8
datanucleus-rdbms 5.2.9
datanucleus-jdo-query 5.0.9

Removing datanucleus-api-jdo will make your life much harder since then you 
will be testing DataNucleus with NO SUPPORT for the JDO API. That is the DN 
API-support jar, not the API interfaces. Just like the associated datanucleus-
api-jpa jar provides SUPPORT for the JPA API.



Regards
-- 
Andy
DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)