Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Werner Keil]

If it passed then it's fine.
There have been quite a few that already failed in the first step.

Julian Feinauer  schrieb am Do., 7. Nov.
2019, 13:36:

> Hi Werner,
>
> for podlings there are two votes.
> First the PPMC Vote (where you voted) and then if that passes an IPMC Vote.
> The second one is a formally binding vote for an Apache Release.
> A PPMC Vote alone is not (as its formally not an Apache PMC).
>
> Thus, two votes and the second one just finished : )
>
> Julian
>
> Am 07.11.19, 13:31 schrieb "Werner Keil" :
>
> I recall I voted on that already
>
> Anatole Tresch  schrieb am Do., 7. Nov. 2019,
> 11:53:
>
> > Great, thanks to all.
> >
> > I assume I will push out everything tomorrow or the WE. I will close
> the
> > vote in the next minutes...
> >
> > J Anatole
> >
> >
> > Am Do., 7. Nov. 2019 um 08:05 Uhr schrieb Julian Feinauer <
> > j.feina...@pragmaticminds.de>:
> >
> > >  and release to maven central via nexus : )
> > >
> > > Julian
> > >
> > > Am 07.11.19, 06:53 schrieb "P. Ottlinger" :
> > >
> > > Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> > > > Hi, we just got the final 2 IPMC Votes, so you can finally
> finish
> > of
> > > the Release Anatole!
> > >
> > > @Julian,
> > > thanks :-)
> > >
> > > I did not change the board report  but this gives us the
> chance
> > to
> > > report something in the next cycle.
> > >
> > > @Anatole: I'm on a trade fair the coming days and will be
> unable to
> > > push
> > > the homepage changes; but the existing 0.4...-something branch
> should
> > > be
> > > the one to merge and push to get the new version out ;)
> > >
> > > Cheers,
> > > Phil
> > >
> > >
> > >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com 
> *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>
>
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Julian Feinauer]

Hi Werner,

for podlings there are two votes.
First the PPMC Vote (where you voted) and then if that passes an IPMC Vote.
The second one is a formally binding vote for an Apache Release.
A PPMC Vote alone is not (as its formally not an Apache PMC).

Thus, two votes and the second one just finished : )

Julian

Am 07.11.19, 13:31 schrieb "Werner Keil" :

I recall I voted on that already

Anatole Tresch  schrieb am Do., 7. Nov. 2019, 11:53:

> Great, thanks to all.
>
> I assume I will push out everything tomorrow or the WE. I will close the
> vote in the next minutes...
>
> J Anatole
>
>
> Am Do., 7. Nov. 2019 um 08:05 Uhr schrieb Julian Feinauer <
> j.feina...@pragmaticminds.de>:
>
> >  and release to maven central via nexus : )
> >
> > Julian
> >
> > Am 07.11.19, 06:53 schrieb "P. Ottlinger" :
> >
> > Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> > > Hi, we just got the final 2 IPMC Votes, so you can finally finish
> of
> > the Release Anatole!
> >
> > @Julian,
> > thanks :-)
> >
> > I did not change the board report  but this gives us the chance
> to
> > report something in the next cycle.
> >
> > @Anatole: I'm on a trade fair the coming days and will be unable to
> > push
> > the homepage changes; but the existing 0.4...-something branch 
should
> > be
> > the one to merge and push to get the new version out ;)
> >
> > Cheers,
> > Phil
> >
> >
> >
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com  *
> *Twitter:  @atsticks, @tamayaconf*
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Werner Keil]

I recall I voted on that already

Anatole Tresch  schrieb am Do., 7. Nov. 2019, 11:53:

> Great, thanks to all.
>
> I assume I will push out everything tomorrow or the WE. I will close the
> vote in the next minutes...
>
> J Anatole
>
>
> Am Do., 7. Nov. 2019 um 08:05 Uhr schrieb Julian Feinauer <
> j.feina...@pragmaticminds.de>:
>
> >  and release to maven central via nexus : )
> >
> > Julian
> >
> > Am 07.11.19, 06:53 schrieb "P. Ottlinger" :
> >
> > Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> > > Hi, we just got the final 2 IPMC Votes, so you can finally finish
> of
> > the Release Anatole!
> >
> > @Julian,
> > thanks :-)
> >
> > I did not change the board report  but this gives us the chance
> to
> > report something in the next cycle.
> >
> > @Anatole: I'm on a trade fair the coming days and will be unable to
> > push
> > the homepage changes; but the existing 0.4...-something branch should
> > be
> > the one to merge and push to get the new version out ;)
> >
> > Cheers,
> > Phil
> >
> >
> >
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com  *
> *Twitter:  @atsticks, @tamayaconf*
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Anatole Tresch]

Great, thanks to all.

I assume I will push out everything tomorrow or the WE. I will close the
vote in the next minutes...

J Anatole


Am Do., 7. Nov. 2019 um 08:05 Uhr schrieb Julian Feinauer <
j.feina...@pragmaticminds.de>:

>  and release to maven central via nexus : )
>
> Julian
>
> Am 07.11.19, 06:53 schrieb "P. Ottlinger" :
>
> Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> > Hi, we just got the final 2 IPMC Votes, so you can finally finish of
> the Release Anatole!
>
> @Julian,
> thanks :-)
>
> I did not change the board report  but this gives us the chance to
> report something in the next cycle.
>
> @Anatole: I'm on a trade fair the coming days and will be unable to
> push
> the homepage changes; but the existing 0.4...-something branch should
> be
> the one to merge and push to get the new version out ;)
>
> Cheers,
> Phil
>
>
>

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Julian Feinauer]

 and release to maven central via nexus : )

Julian

Am 07.11.19, 06:53 schrieb "P. Ottlinger" :

Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> Hi, we just got the final 2 IPMC Votes, so you can finally finish of the 
Release Anatole!

@Julian,
thanks :-)

I did not change the board report  but this gives us the chance to
report something in the next cycle.

@Anatole: I'm on a trade fair the coming days and will be unable to push
the homepage changes; but the existing 0.4...-something branch should be
the one to merge and push to get the new version out ;)

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[P. Ottlinger]

Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> Hi, we just got the final 2 IPMC Votes, so you can finally finish of the 
> Release Anatole!

@Julian,
thanks :-)

I did not change the board report  but this gives us the chance to
report something in the next cycle.

@Anatole: I'm on a trade fair the coming days and will be unable to push
the homepage changes; but the existing 0.4...-something branch should be
the one to merge and push to get the new version out ;)

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Julian Feinauer]

Hi, we just got the final 2 IPMC Votes, so you can finally finish of the 
Release Anatole!

Good job!

Julian

Am 23.10.19, 09:09 schrieb "Anatole Tresch" :

Hi,

The Tamaya team was running the needed tasks to get the 0.4-incubating
release of Tamaya out.
The artifacts available via the Apache distribution repository [1] and
also via Apache's Nexus [2].

The tag for this release candidate is available at [3] and [4]. It will be
renamed
once the vote passed.

The mail thread of the vote can be found at [5].

Please take a look at the artifacts and vote!

Please note:
This vote is a "majority approval" with a minimum of three +1 votes (see
[6]).
Hereby we already have one binding +1 vote carrying over from our PPMC vote
by our mentor Julian Feinauer [7]


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/

[2] https://repository.apache.org/content/repositories/orgapachetamaya-1040
[3]

https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=0ad439201f16ba1ddcc6b5c9ffb65e0a8a067301
[4]

https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;a=commit;h=a397bf7cf08ec57830aabe7b66099e70390a5006

[5]

https://lists.apache.org/thread.html/7f52e8bcac7f8d60205179b632416ff24cadd64b5f45c38f42f87e38@%3Cdev.tamaya.apache.org%3E

[6] http://www.apache.org/foundation/voting.html#ReleaseVotes
[7]

https://lists.apache.org/thread.html/c56ada758367709f0b9a86712ebc3cea62b799e4c44a057ee87d7761@%3Cdev.tamaya.apache.org%3E

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [RESULT][VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Julian Feinauer]

Hi Anatole,

thanks and gratz!
As I am IPMC member my vote carries over to the incubator vote, so you can 
already state in your vote mail my +1 (so only 2 more needed).

Best
Julian

Am 08.10.19, 09:02 schrieb "Anatole Tresch" :

I am happy to close thiis vote with an overall YES result, in detail:

4 binding +1 votes (PPMC):
  Julian Feinauer
  Anatole Tresch
  Werner Keil
  Phil Ottlinger

2 non-binding +1 votes:
  William Lieurance
  Aaaron Coburn

0 -1 votes.

I will open the incubator vote within next days.

J Anatole

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[RESULT][VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Anatole Tresch]

I am happy to close thiis vote with an overall YES result, in detail:

4 binding +1 votes (PPMC):
  Julian Feinauer
  Anatole Tresch
  Werner Keil
  Phil Ottlinger

2 non-binding +1 votes:
  William Lieurance
  Aaaron Coburn

0 -1 votes.

I will open the incubator vote within next days.

J Anatole

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Anatole Tresch]

Obviously also +1 from my side.

Am Mi., 2. Okt. 2019 um 13:40 Uhr schrieb Julian Feinauer <
j.feina...@pragmaticminds.de>:

> Hi all,
>
> sorry for being late to the party, my vote is
>
> +1 (binding, carries over to IPMC Vote also)
>
> great Job Anatole!
>
> I checked:
> - Hashes and Signature is are okay for apicore and extension (now with
> sha512 and asc)
> - NOTICE, LICENCE and DISCLAIMER look good
> - Checked instructions in readme
> - License headers on source codes look fine
> - No unexpected binaries
> - Able to compile both sources using 'mvn clean install' on MacOS Mojave
> using java 8.
>
> Minor Comment:
> - staged are also sha512 hashes for the asc files which is unnecessary and
> should be removed when we bring it to dist
>
> Best
> Julian
>
> Am 02.10.19, 09:32 schrieb "Werner Keil" :
>
> +1
> Werner
>
> P. Ottlinger  schrieb am Mi., 2. Okt. 2019,
> 07:48:
>
> > Am 25.09.19 um 14:41 schrieb Anatole Tresch:
> > > The tag for this release candidate is available at [3] and [4]. It
> will
> > be
> > > renamed
> > > once the vote passed.
> > > Please take a look at the artifacts and vote!
> >
> > +1
> >
> > Works fine in my pet project.
> >
> > Cheers,
> > Phil
> >
>
>
>

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Julian Feinauer]

Hi all,

sorry for being late to the party, my vote is

+1 (binding, carries over to IPMC Vote also)

great Job Anatole!

I checked:
- Hashes and Signature is are okay for apicore and extension (now with sha512 
and asc)
- NOTICE, LICENCE and DISCLAIMER look good
- Checked instructions in readme
- License headers on source codes look fine
- No unexpected binaries
- Able to compile both sources using 'mvn clean install' on MacOS Mojave using 
java 8.

Minor Comment:
- staged are also sha512 hashes for the asc files which is unnecessary and 
should be removed when we bring it to dist

Best
Julian

Am 02.10.19, 09:32 schrieb "Werner Keil" :

+1
Werner

P. Ottlinger  schrieb am Mi., 2. Okt. 2019, 07:48:

> Am 25.09.19 um 14:41 schrieb Anatole Tresch:
> > The tag for this release candidate is available at [3] and [4]. It will
> be
> > renamed
> > once the vote passed.
> > Please take a look at the artifacts and vote!
>
> +1
>
> Works fine in my pet project.
>
> Cheers,
> Phil
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Werner Keil]

+1
Werner

P. Ottlinger  schrieb am Mi., 2. Okt. 2019, 07:48:

> Am 25.09.19 um 14:41 schrieb Anatole Tresch:
> > The tag for this release candidate is available at [3] and [4]. It will
> be
> > renamed
> > once the vote passed.
> > Please take a look at the artifacts and vote!
>
> +1
>
> Works fine in my pet project.
>
> Cheers,
> Phil
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[P. Ottlinger]

Am 25.09.19 um 14:41 schrieb Anatole Tresch:
> The tag for this release candidate is available at [3] and [4]. It will be
> renamed
> once the vote passed.
> Please take a look at the artifacts and vote!

+1

Works fine in my pet project.

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[William Lieurance]

+1 from me as well.

I verified that the code compiles cleanly and passes the same tests as it 
normally does.  Signatures and checksums all match.  

Clearly we shouldn't publish md5s or sha1s, but I don't take a position on 
whether that should block this release.

--William


From: Aaron Coburn 
Sent: Wednesday, September 25, 2019 11:18 AM
To: dev@tamaya.incubator.apache.org
Subject: Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

+1

I verified the signatures and hashes for API/Core and Extensions artifacts
(Note: in the future, you don't need to include *all of* md5, sha1, sha256
and sha512; just including one of sha512 or sha256 will suffice)

The core and ext code builds and all the tests pass.

I have some downstream projects that use the CDI and microprofile
extensions, and those work correctly with the RC artifacts

The LICENSE files look correct to me (mvn apache-rat:check passes for both
core and ext), and the files are present in the compiled JARs. Ditto with
the NOTICE files.

Cheers,
Aaron



On Wed, 25 Sep 2019 at 08:42, Anatole Tresch  wrote:

> Hi,
>
> I was running the needed tasks to get the 0.4-incubating release of Tamaya
> out.
> The artifacts available via the Apache distribution repository [1] and
> also via Apache's Nexus [2].
>
> The tag for this release candidate is available at [3] and [4]. It will be
> renamed
> once the vote passed.
> Please take a look at the artifacts and vote!
>
> Please note:
> This vote is a "majority approval" with a minimum of three +1 votes (see
> [5]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be released, and
> why ...
> 
>
> Thanks,
> Anatole Tresch
>
> [1]
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
>
> [2]
> https://repository.apache.org/content/repositories/orgapachetamaya-1040
> [3]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=0ad439201f16ba1ddcc6b5c9ffb65e0a8a067301
> [4]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;a=commit;h=a397bf7cf08ec57830aabe7b66099e70390a5006
>
> [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
>
> *Twitter:  @atsticks, @tamayaconf*
> *http://tamaya.incubator.apache.org  <http://tamaya.incubator.apache.org>*
> http://javamoney.org
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Julian Feinauer]

Ah, thanks fort he clarification, didnt know that.. so I would go with asc and 
sha512 : )

Am 26.09.19, 01:39 schrieb "Justin Mclean" :

Hi,

> we use asc for signing and sha256 or 512 is common for checksum, I think.
> This is used in many projects and should be fine and up to date.

That correct but you also have sha1 and md5s.

> @Justin Mclean or is there any official rule or policy about that?

Yes see [1] note the "and SHOULD NOT supply MD5 or SHA-1”.

Thanks,
Justin

1. https://www.apache.org/dev/release-distribution.html#sigs-and-sums

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Justin Mclean]

Hi,

> we use asc for signing and sha256 or 512 is common for checksum, I think.
> This is used in many projects and should be fine and up to date.

That correct but you also have sha1 and md5s.

> @Justin Mclean or is there any official rule or policy about that?

Yes see [1] note the "and SHOULD NOT supply MD5 or SHA-1”.

Thanks,
Justin

1. https://www.apache.org/dev/release-distribution.html#sigs-and-sums

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Aaron Coburn]

+1

I verified the signatures and hashes for API/Core and Extensions artifacts
(Note: in the future, you don't need to include *all of* md5, sha1, sha256
and sha512; just including one of sha512 or sha256 will suffice)

The core and ext code builds and all the tests pass.

I have some downstream projects that use the CDI and microprofile
extensions, and those work correctly with the RC artifacts

The LICENSE files look correct to me (mvn apache-rat:check passes for both
core and ext), and the files are present in the compiled JARs. Ditto with
the NOTICE files.

Cheers,
Aaron



On Wed, 25 Sep 2019 at 08:42, Anatole Tresch  wrote:

> Hi,
>
> I was running the needed tasks to get the 0.4-incubating release of Tamaya
> out.
> The artifacts available via the Apache distribution repository [1] and
> also via Apache's Nexus [2].
>
> The tag for this release candidate is available at [3] and [4]. It will be
> renamed
> once the vote passed.
> Please take a look at the artifacts and vote!
>
> Please note:
> This vote is a "majority approval" with a minimum of three +1 votes (see
> [5]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be released, and
> why ...
> 
>
> Thanks,
> Anatole Tresch
>
> [1]
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
>
> [2]
> https://repository.apache.org/content/repositories/orgapachetamaya-1040
> [3]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=0ad439201f16ba1ddcc6b5c9ffb65e0a8a067301
> [4]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;a=commit;h=a397bf7cf08ec57830aabe7b66099e70390a5006
>
> [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
>
> *Twitter:  @atsticks, @tamayaconf*
> *http://tamaya.incubator.apache.org  *
> http://javamoney.org
>

[VOTE] Release of Apache Tamaya 0.4-incubating-RC5

[Anatole Tresch]

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache distribution repository [1] and
also via Apache's Nexus [2].

The tag for this release candidate is available at [3] and [4]. It will be
renamed
once the vote passed.
Please take a look at the artifacts and vote!

Please note:
This vote is a "majority approval" with a minimum of three +1 votes (see
[5]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/

[2] https://repository.apache.org/content/repositories/orgapachetamaya-1040
[3]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=0ad439201f16ba1ddcc6b5c9ffb65e0a8a067301
[4]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;a=commit;h=a397bf7cf08ec57830aabe7b66099e70390a5006

[5] http://www.apache.org/foundation/voting.html#ReleaseVotes


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*

*Twitter:  @atsticks, @tamayaconf*
*http://tamaya.incubator.apache.org  *
http://javamoney.org

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Julian Feinauer]

Hi,

we use asc for signing and sha256 or 512 is common for checksum, I think.
This is used in many projects and should be fine and up to date.

@Justin Mclean or is there any official rule or policy about that?

Julian

Am 25.09.19, 12:49 schrieb "Anatole Tresch" :

Found:

   - .asc for a (ASCII-armored) PGP signature
   - .md5 for a MD5 checksum
   - .sha1 for a SHA-1 checksum
   - .sha256 for a SHA-256 checksum, will be added
   - .sha512 for a SHA-512 checksum, will be added


Am Mi., 25. Sept. 2019 um 12:42 Uhr schrieb Anatole Tresch <
atsti...@gmail.com>:

> Does anybody see what are the correct hashes now needed? sha1 and md5 are
> still there in most projects in https://dist.apache.org/repos/dist/release
> 
> Some also have sha512 which I can easily add, I think. What is the exact
> requirement?
>
> J Anatole
>
>
>
> Am Mo., 16. Sept. 2019 um 17:43 Uhr schrieb Julian Feinauer <
> j.feina...@pragmaticminds.de>:
>
>> Hi all,
>>
>> +1 (binding, carries over to IPMC Vote also)
>>
>> I checked:
>> - Hashes and Signature is are okay for apicore and extension
>> - NOTICE, LICENCE and DISCLAIMER look good
>> - Checked instructions in readme
>> - License headers on source codes look fine
>> - No unexpected binaries
>> - Able to compile both sources using 'mvn clean install' on MacOS Mojave
>> using java 8.
>>
>> Very well done, Anatole!
>>
>> Julian
>>
>> Am 13.09.19, 04:49 schrieb "Werner Keil" :
>>
>> Cool, then also
>>
>> +1
>> from my side.
>>
>> Hope it all works this time?
>>
>> Werner
>>
>>
>>
>> On Fri, Sep 13, 2019 at 1:06 PM Aaron Coburn 
>> wrote:
>>
>> > +1
>> >
>> > I verified the signatures and hashes for the api/core release as
>> well as
>> > for the extensions.
>> > The code built correctly for me using Java 11 on a Mac:
>> >
>> > $ java -version
>> > java version "11.0.3" 2019-04-16 LTS
>> > Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
>> > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed
>> mode)
>> >
>> > The `mvn apache-rat:check` task looks good w/r/t license files
>> >
>> > And finally, I have a downstream project that uses the microprofile
>> and cdi
>> > extensions, and that code all worked correctly when using the
>> artifacts
>> > built from this release candidate.
>> >
>> > Thanks for pulling this together.
>> >
>> > Aaron
>> >
>> > On Thu, 12 Sep 2019 at 09:45, Anatole Tresch 
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > I was running the needed tasks to get the 0.4-incubating release
>> of
>> > Tamaya
>> > > out.
>> > > The artifacts available via the Apache distribution repository
>> [1] and
>> > > also via Apache's Nexus [2].
>> > >
>> > > The tag for this release candidate is available at [3] and will 
be
>> > renamed
>> > > once the vote passed.
>> > > Please take a look at the artifacts and vote!
>> > >
>> > > Please note:
>> > > This vote is a "majority approval" with a minimum of three +1
>> votes (see
>> > > [4]).
>> > >
>> > > 
>> > > [ ] +1 for community members who have reviewed the bits
>> > > [ ] +0
>> > > [ ] -1 for fatal flaws that should cause these bits not to be
>> released,
>> > and
>> > > why ...
>> > > 
>> > >
>> > > Thanks,
>> > > Anatole Tresch
>> > >
>> > > [1]
>> > >
>> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
>> > >
>> > > [2]
>> > >
>> https://repository.apache.org/content/repositories/orgapachetamaya-1039
>> > > [3]
>> > >
>> > >
>> >
>> 
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472
>> > >
>> > > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > *Anatole Tresch*
>> > > PPMC Member Apache Tamaya
>> > > JCP Star Spec Lead
>> > > *Switzerland, Europe Zurich, GMT+1*
>> > > *maketechsimple.wordpress.com <
>> http://maketechsimple.wordpress.com/> *
>> > > *Twitter:  @atsticks, @tamayaconf*
>> > >
>> >
>>
>>
>>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Anatole Tresch]

Found:

   - .asc for a (ASCII-armored) PGP signature
   - .md5 for a MD5 checksum
   - .sha1 for a SHA-1 checksum
   - .sha256 for a SHA-256 checksum, will be added
   - .sha512 for a SHA-512 checksum, will be added


Am Mi., 25. Sept. 2019 um 12:42 Uhr schrieb Anatole Tresch <
atsti...@gmail.com>:

> Does anybody see what are the correct hashes now needed? sha1 and md5 are
> still there in most projects in https://dist.apache.org/repos/dist/release
> 
> Some also have sha512 which I can easily add, I think. What is the exact
> requirement?
>
> J Anatole
>
>
>
> Am Mo., 16. Sept. 2019 um 17:43 Uhr schrieb Julian Feinauer <
> j.feina...@pragmaticminds.de>:
>
>> Hi all,
>>
>> +1 (binding, carries over to IPMC Vote also)
>>
>> I checked:
>> - Hashes and Signature is are okay for apicore and extension
>> - NOTICE, LICENCE and DISCLAIMER look good
>> - Checked instructions in readme
>> - License headers on source codes look fine
>> - No unexpected binaries
>> - Able to compile both sources using 'mvn clean install' on MacOS Mojave
>> using java 8.
>>
>> Very well done, Anatole!
>>
>> Julian
>>
>> Am 13.09.19, 04:49 schrieb "Werner Keil" :
>>
>> Cool, then also
>>
>> +1
>> from my side.
>>
>> Hope it all works this time?
>>
>> Werner
>>
>>
>>
>> On Fri, Sep 13, 2019 at 1:06 PM Aaron Coburn 
>> wrote:
>>
>> > +1
>> >
>> > I verified the signatures and hashes for the api/core release as
>> well as
>> > for the extensions.
>> > The code built correctly for me using Java 11 on a Mac:
>> >
>> > $ java -version
>> > java version "11.0.3" 2019-04-16 LTS
>> > Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
>> > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed
>> mode)
>> >
>> > The `mvn apache-rat:check` task looks good w/r/t license files
>> >
>> > And finally, I have a downstream project that uses the microprofile
>> and cdi
>> > extensions, and that code all worked correctly when using the
>> artifacts
>> > built from this release candidate.
>> >
>> > Thanks for pulling this together.
>> >
>> > Aaron
>> >
>> > On Thu, 12 Sep 2019 at 09:45, Anatole Tresch 
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > I was running the needed tasks to get the 0.4-incubating release
>> of
>> > Tamaya
>> > > out.
>> > > The artifacts available via the Apache distribution repository
>> [1] and
>> > > also via Apache's Nexus [2].
>> > >
>> > > The tag for this release candidate is available at [3] and will be
>> > renamed
>> > > once the vote passed.
>> > > Please take a look at the artifacts and vote!
>> > >
>> > > Please note:
>> > > This vote is a "majority approval" with a minimum of three +1
>> votes (see
>> > > [4]).
>> > >
>> > > 
>> > > [ ] +1 for community members who have reviewed the bits
>> > > [ ] +0
>> > > [ ] -1 for fatal flaws that should cause these bits not to be
>> released,
>> > and
>> > > why ...
>> > > 
>> > >
>> > > Thanks,
>> > > Anatole Tresch
>> > >
>> > > [1]
>> > >
>> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
>> > >
>> > > [2]
>> > >
>> https://repository.apache.org/content/repositories/orgapachetamaya-1039
>> > > [3]
>> > >
>> > >
>> >
>> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472
>> > >
>> > > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > *Anatole Tresch*
>> > > PPMC Member Apache Tamaya
>> > > JCP Star Spec Lead
>> > > *Switzerland, Europe Zurich, GMT+1*
>> > > *maketechsimple.wordpress.com <
>> http://maketechsimple.wordpress.com/> *
>> > > *Twitter:  @atsticks, @tamayaconf*
>> > >
>> >
>>
>>
>>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com  *
> *Twitter:  @atsticks, @tamayaconf*
>
>
>

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Anatole Tresch]

Does anybody see what are the correct hashes now needed? sha1 and md5 are
still there in most projects in https://dist.apache.org/repos/dist/release

Some also have sha512 which I can easily add, I think. What is the exact
requirement?

J Anatole



Am Mo., 16. Sept. 2019 um 17:43 Uhr schrieb Julian Feinauer <
j.feina...@pragmaticminds.de>:

> Hi all,
>
> +1 (binding, carries over to IPMC Vote also)
>
> I checked:
> - Hashes and Signature is are okay for apicore and extension
> - NOTICE, LICENCE and DISCLAIMER look good
> - Checked instructions in readme
> - License headers on source codes look fine
> - No unexpected binaries
> - Able to compile both sources using 'mvn clean install' on MacOS Mojave
> using java 8.
>
> Very well done, Anatole!
>
> Julian
>
> Am 13.09.19, 04:49 schrieb "Werner Keil" :
>
> Cool, then also
>
> +1
> from my side.
>
> Hope it all works this time?
>
> Werner
>
>
>
> On Fri, Sep 13, 2019 at 1:06 PM Aaron Coburn 
> wrote:
>
> > +1
> >
> > I verified the signatures and hashes for the api/core release as
> well as
> > for the extensions.
> > The code built correctly for me using Java 11 on a Mac:
> >
> > $ java -version
> > java version "11.0.3" 2019-04-16 LTS
> > Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
> > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed
> mode)
> >
> > The `mvn apache-rat:check` task looks good w/r/t license files
> >
> > And finally, I have a downstream project that uses the microprofile
> and cdi
> > extensions, and that code all worked correctly when using the
> artifacts
> > built from this release candidate.
> >
> > Thanks for pulling this together.
> >
> > Aaron
> >
> > On Thu, 12 Sep 2019 at 09:45, Anatole Tresch 
> wrote:
> >
> > > Hi,
> > >
> > > I was running the needed tasks to get the 0.4-incubating release of
> > Tamaya
> > > out.
> > > The artifacts available via the Apache distribution repository [1]
> and
> > > also via Apache's Nexus [2].
> > >
> > > The tag for this release candidate is available at [3] and will be
> > renamed
> > > once the vote passed.
> > > Please take a look at the artifacts and vote!
> > >
> > > Please note:
> > > This vote is a "majority approval" with a minimum of three +1
> votes (see
> > > [4]).
> > >
> > > 
> > > [ ] +1 for community members who have reviewed the bits
> > > [ ] +0
> > > [ ] -1 for fatal flaws that should cause these bits not to be
> released,
> > and
> > > why ...
> > > 
> > >
> > > Thanks,
> > > Anatole Tresch
> > >
> > > [1]
> > >
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
> > >
> > > [2]
> > >
> https://repository.apache.org/content/repositories/orgapachetamaya-1039
> > > [3]
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472
> > >
> > > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
> > >
> > >
> > >
> > >
> > >
> > > --
> > > *Anatole Tresch*
> > > PPMC Member Apache Tamaya
> > > JCP Star Spec Lead
> > > *Switzerland, Europe Zurich, GMT+1*
> > > *maketechsimple.wordpress.com <
> http://maketechsimple.wordpress.com/> *
> > > *Twitter:  @atsticks, @tamayaconf*
> > >
> >
>
>
>

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[RESULT][VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Anatole Tresch]

Since there are still minor issues with some checksums I close this vote
with a NO result.
Lets go for RC5 and keep fingers crossed!

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Justin Mclean]

Hi ,

Julian contacted me off-list and asked me to take a look at your release.

I suggest you create a checklist for the release (see the one of the incubator 
wiki page for a good example).

I'm about to board a flight and had a chance to take a quick look. I can see 
only a couple of minor issues:
- Your checksum need to be updated md5 and sha1 are no longer used.
- You NOTICE file copyright year is not unto date.

Everything else looks good to me.

Not having the right hashes would likely fail an incubator vote, as you are not 
using the work in progress disclaimer, but is easily fixed without re-voting 
here.

Thanks,
Justin

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Julian Feinauer]

Hi all,

+1 (binding, carries over to IPMC Vote also)

I checked:
- Hashes and Signature is are okay for apicore and extension
- NOTICE, LICENCE and DISCLAIMER look good
- Checked instructions in readme
- License headers on source codes look fine
- No unexpected binaries
- Able to compile both sources using 'mvn clean install' on MacOS Mojave using 
java 8.

Very well done, Anatole!

Julian

Am 13.09.19, 04:49 schrieb "Werner Keil" :

Cool, then also

+1
from my side.

Hope it all works this time?

Werner



On Fri, Sep 13, 2019 at 1:06 PM Aaron Coburn  wrote:

> +1
>
> I verified the signatures and hashes for the api/core release as well as
> for the extensions.
> The code built correctly for me using Java 11 on a Mac:
>
> $ java -version
> java version "11.0.3" 2019-04-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed mode)
>
> The `mvn apache-rat:check` task looks good w/r/t license files
>
> And finally, I have a downstream project that uses the microprofile and 
cdi
> extensions, and that code all worked correctly when using the artifacts
> built from this release candidate.
>
> Thanks for pulling this together.
>
> Aaron
>
> On Thu, 12 Sep 2019 at 09:45, Anatole Tresch  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 0.4-incubating release of
> Tamaya
> > out.
> > The artifacts available via the Apache distribution repository [1] and
> > also via Apache's Nexus [2].
> >
> > The tag for this release candidate is available at [3] and will be
> renamed
> > once the vote passed.
> > Please take a look at the artifacts and vote!
> >
> > Please note:
> > This vote is a "majority approval" with a minimum of three +1 votes (see
> > [4]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why ...
> > 
> >
> > Thanks,
> > Anatole Tresch
> >
> > [1]
> > https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
> >
> > [2]
> > https://repository.apache.org/content/repositories/orgapachetamaya-1039
> > [3]
> >
> >
> 
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472
> >
> > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
> >
> >
> >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com  *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Werner Keil]

Cool, then also

+1
from my side.

Hope it all works this time?

Werner



On Fri, Sep 13, 2019 at 1:06 PM Aaron Coburn  wrote:

> +1
>
> I verified the signatures and hashes for the api/core release as well as
> for the extensions.
> The code built correctly for me using Java 11 on a Mac:
>
> $ java -version
> java version "11.0.3" 2019-04-16 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed mode)
>
> The `mvn apache-rat:check` task looks good w/r/t license files
>
> And finally, I have a downstream project that uses the microprofile and cdi
> extensions, and that code all worked correctly when using the artifacts
> built from this release candidate.
>
> Thanks for pulling this together.
>
> Aaron
>
> On Thu, 12 Sep 2019 at 09:45, Anatole Tresch  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 0.4-incubating release of
> Tamaya
> > out.
> > The artifacts available via the Apache distribution repository [1] and
> > also via Apache's Nexus [2].
> >
> > The tag for this release candidate is available at [3] and will be
> renamed
> > once the vote passed.
> > Please take a look at the artifacts and vote!
> >
> > Please note:
> > This vote is a "majority approval" with a minimum of three +1 votes (see
> > [4]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why ...
> > 
> >
> > Thanks,
> > Anatole Tresch
> >
> > [1]
> > https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
> >
> > [2]
> > https://repository.apache.org/content/repositories/orgapachetamaya-1039
> > [3]
> >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472
> >
> > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
> >
> >
> >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com  *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Aaron Coburn]

+1

I verified the signatures and hashes for the api/core release as well as
for the extensions.
The code built correctly for me using Java 11 on a Mac:

$ java -version
java version "11.0.3" 2019-04-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed mode)

The `mvn apache-rat:check` task looks good w/r/t license files

And finally, I have a downstream project that uses the microprofile and cdi
extensions, and that code all worked correctly when using the artifacts
built from this release candidate.

Thanks for pulling this together.

Aaron

On Thu, 12 Sep 2019 at 09:45, Anatole Tresch  wrote:

> Hi,
>
> I was running the needed tasks to get the 0.4-incubating release of Tamaya
> out.
> The artifacts available via the Apache distribution repository [1] and
> also via Apache's Nexus [2].
>
> The tag for this release candidate is available at [3] and will be renamed
> once the vote passed.
> Please take a look at the artifacts and vote!
>
> Please note:
> This vote is a "majority approval" with a minimum of three +1 votes (see
> [4]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be released, and
> why ...
> 
>
> Thanks,
> Anatole Tresch
>
> [1]
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
>
> [2]
> https://repository.apache.org/content/repositories/orgapachetamaya-1039
> [3]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472
>
> [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
>
>
>
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com  *
> *Twitter:  @atsticks, @tamayaconf*
>

[VOTE] Release of Apache Tamaya 0.4-incubating-RC4

[Anatole Tresch]

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache distribution repository [1] and
also via Apache's Nexus [2].

The tag for this release candidate is available at [3] and will be renamed
once the vote passed.
Please take a look at the artifacts and vote!

Please note:
This vote is a "majority approval" with a minimum of three +1 votes (see
[4]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/

[2] https://repository.apache.org/content/repositories/orgapachetamaya-1039
[3]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=f9cecfd65b3f5241651813be12b46b8d0cef1472

[4] http://www.apache.org/foundation/voting.html#ReleaseVotes





-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[Result][VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Anatole Tresch]

I will close this vote again with a NO result, let's do another try - stay
tuned and happy ;-)


Am Do., 5. Sept. 2019 um 09:35 Uhr schrieb Julian Feinauer <
j.feina...@pragmaticminds.de>:

> Hi all,
>
> sorry for the late reply.
> I just checked the release.
>
> Sadly, I have to vote
>
> -1 (binding)
>
> as the Signatures that were used to sign the artefacts in extensions
> module are NOT in the keys file and thus cant be checked : /
>
> Furthermore, if trying to build apiandcore (as explained in README) I get
>
> Unrecognized VM option 'PermGenSpace=200m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
>
> On OS X with
> - mvn
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> - java
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> which should also be compliant due to README.
>
> If I disable PermGenSpace then I am able to build both modules
> successfully.
> So I would just delete that form the readme, than it should be fine.
> I think those issues are rather "minor" and not blocking.
>
> Furthermore I checked:
> - Signature is okay for apiandcore
> - No Hash is present (I think that’s okay?!) but it would be good to have
> sha hashes
> - NOTICE, LICENCE and DISCLAIMER look good
> - I found several files without License header (see below). Most of these
> are okay but I would check the bnd files
> - No unexpected binaries
>
> So although I have to downvote the release it looks pretty good and I
> think there are only some small changes necessary to make it pass.
>
> Julian
>
> # Appendix: Files without License header (rat output):
>
> ## Apiandcore
> 24   ./.travis.yml
>  25   ./README.md
>  26   ./maturity-model.md
> 28   ./running-mutation-tests.adoc
>  29   ./code/api/bnd.bnd
>  30   ./code/core/bnd.bnd
>  31   ./code/core/src/test/resources/java-security.policy
>  32   ./code/spi-support/bnd.bnd
>  33   ./readme/ReleaseNotes-0.1-incubating.html
>  34   ./readme/ReleaseNotes-0.2-incubating.html
>  35   ./readme/ReleaseNotes-0.3-incubating.html
>  36   ./readme/ReleaseNotes-0.4-incubating.html
>
> ## Extensions
>   24   ./.travis.yml
>   25   ./README.md
>   28   ./running-mutation-tests.adoc
>   29   ./examples/02-resolver-example/src/main/resources/build.data
>   30   ./examples/05-spring-example/README.md
>   31   ./modules/collections/bnd.bnd
>   32   ./modules/consul/bnd.bnd
>   33   ./modules/etcd/bnd.bnd
>   34   ./modules/etcd/nbactions.xml
>   35   ./modules/events/bnd.bnd
>   36   ./modules/features/bnd.bnd
>   37   ./modules/filter/bnd.bnd
>   38   ./modules/formats/base/bnd.bnd
>   39   ./modules/formats/hocon/bnd.bnd
>   40   ./modules/formats/json/bnd.bnd
>   41   ./modules/formats/yaml/bnd.bnd
>   42   ./modules/functions/bnd.bnd
>   43   ./modules/hazelcast/bnd.bnd
>   44   ./modules/injection/cdi/bnd.bnd
>   45   ./modules/injection/injection-api/bnd.bnd
>   46   ./modules/injection/standalone/bnd.bnd
>   47   ./modules/jndi/bnd.bnd
>   48   ./modules/microprofile/bnd.bnd
>   49   ./modules/mutable-config/bnd.bnd
>   50   ./modules/optional/bnd.bnd
>   51   ./modules/osgi/common/bnd.bnd
>   52   ./modules/osgi/gogo-shell/bnd.bnd
>   53   ./modules/osgi/injection/bnd.bnd
>   54   ./modules/osgi/karaf-shell/bnd.bnd
>   55   ./modules/osgi/updater/bnd.bnd
>   56   ./modules/resolver/bnd.bnd
>   57   ./modules/resources/README.md
>   58   ./modules/resources/bnd.bnd
>   59   ./modules/spring/bnd.bnd
>
>
> Am 01.09.19, 08:58 schrieb "P. Ottlinger" :
>
> Am 28.08.19 um 03:00 schrieb Anatole Tresch:
> > [ ] +1 for community members who have reviewed the bits
>
> +1
>
> I played with the core artifacts and checked the homepage changes.
>
> Did not look into much detail into sandbox and extensions, but core
> looks fine.
>
> Cheers,
> Phil
>
>
>

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Anatole Tresch]

Hi all

thanks. Interesting so much things still pop up since it is not our first
release, but basically all issues found are good, do lets fix them and
bundle another release. I will may clean my complete setup here so
definitively no old key is laying around ;-)

If all works fine, I can do the work needed on Thursday. Can anybody else
prepare the also overdue report? I was not able to do it in time, sorry.

J Anatole


Am Do., 5. Sept. 2019 um 09:35 Uhr schrieb Julian Feinauer <
j.feina...@pragmaticminds.de>:

> Hi all,
>
> sorry for the late reply.
> I just checked the release.
>
> Sadly, I have to vote
>
> -1 (binding)
>
> as the Signatures that were used to sign the artefacts in extensions
> module are NOT in the keys file and thus cant be checked : /
>
> Furthermore, if trying to build apiandcore (as explained in README) I get
>
> Unrecognized VM option 'PermGenSpace=200m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
>
> On OS X with
> - mvn
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> - java
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> which should also be compliant due to README.
>
> If I disable PermGenSpace then I am able to build both modules
> successfully.
> So I would just delete that form the readme, than it should be fine.
> I think those issues are rather "minor" and not blocking.
>
> Furthermore I checked:
> - Signature is okay for apiandcore
> - No Hash is present (I think that’s okay?!) but it would be good to have
> sha hashes
> - NOTICE, LICENCE and DISCLAIMER look good
> - I found several files without License header (see below). Most of these
> are okay but I would check the bnd files
> - No unexpected binaries
>
> So although I have to downvote the release it looks pretty good and I
> think there are only some small changes necessary to make it pass.
>
> Julian
>
> # Appendix: Files without License header (rat output):
>
> ## Apiandcore
> 24   ./.travis.yml
>  25   ./README.md
>  26   ./maturity-model.md
> 28   ./running-mutation-tests.adoc
>  29   ./code/api/bnd.bnd
>  30   ./code/core/bnd.bnd
>  31   ./code/core/src/test/resources/java-security.policy
>  32   ./code/spi-support/bnd.bnd
>  33   ./readme/ReleaseNotes-0.1-incubating.html
>  34   ./readme/ReleaseNotes-0.2-incubating.html
>  35   ./readme/ReleaseNotes-0.3-incubating.html
>  36   ./readme/ReleaseNotes-0.4-incubating.html
>
> ## Extensions
>   24   ./.travis.yml
>   25   ./README.md
>   28   ./running-mutation-tests.adoc
>   29   ./examples/02-resolver-example/src/main/resources/build.data
>   30   ./examples/05-spring-example/README.md
>   31   ./modules/collections/bnd.bnd
>   32   ./modules/consul/bnd.bnd
>   33   ./modules/etcd/bnd.bnd
>   34   ./modules/etcd/nbactions.xml
>   35   ./modules/events/bnd.bnd
>   36   ./modules/features/bnd.bnd
>   37   ./modules/filter/bnd.bnd
>   38   ./modules/formats/base/bnd.bnd
>   39   ./modules/formats/hocon/bnd.bnd
>   40   ./modules/formats/json/bnd.bnd
>   41   ./modules/formats/yaml/bnd.bnd
>   42   ./modules/functions/bnd.bnd
>   43   ./modules/hazelcast/bnd.bnd
>   44   ./modules/injection/cdi/bnd.bnd
>   45   ./modules/injection/injection-api/bnd.bnd
>   46   ./modules/injection/standalone/bnd.bnd
>   47   ./modules/jndi/bnd.bnd
>   48   ./modules/microprofile/bnd.bnd
>   49   ./modules/mutable-config/bnd.bnd
>   50   ./modules/optional/bnd.bnd
>   51   ./modules/osgi/common/bnd.bnd
>   52   ./modules/osgi/gogo-shell/bnd.bnd
>   53   ./modules/osgi/injection/bnd.bnd
>   54   ./modules/osgi/karaf-shell/bnd.bnd
>   55   ./modules/osgi/updater/bnd.bnd
>   56   ./modules/resolver/bnd.bnd
>   57   ./modules/resources/README.md
>   58   ./modules/resources/bnd.bnd
>   59   ./modules/spring/bnd.bnd
>
>
> Am 01.09.19, 08:58 schrieb "P. Ottlinger" :
>
> Am 28.08.19 um 03:00 schrieb Anatole Tresch:
> > [ ] +1 for community members who have reviewed the bits
>
> +1
>
> I played with the core artifacts and checked the homepage changes.
>
> Did not look into much detail into sandbox and extensions, but core
> looks fine.
>
> Cheers,
> Phil
>
>
>

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Julian Feinauer]

Hi Phil,

Its not a question about what we think.. its about the ASF policy : )

Policy [1] says 

"Source files consisting of works submitted directly to the ASF by the 
copyright owner or owner's agent must contain the appropriate ASF license 
header."

Thus, I would prefer to have it in if we agree that its some kind of source.

Julian

[1] https://apache.org/legal/release-policy.html#license-headers

Am 06.09.19, 00:04 schrieb "P. Ottlinger" :

Am 05.09.19 um 21:00 schrieb Julian Feinauer:
> yeah I think we should have another RC... : /


Should we exclude bnd files and markdown from RAT scans?

I think it does not make sense to pollute the bnd files with license
heeaders.

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[P. Ottlinger]

Am 05.09.19 um 21:00 schrieb Julian Feinauer:
> yeah I think we should have another RC... : /


Should we exclude bnd files and markdown from RAT scans?

I think it does not make sense to pollute the bnd files with license
heeaders.

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Julian Feinauer]

Hi,

yeah I think we should have another RC... : /

Julian

Am 05.09.19, 20:04 schrieb "Werner Keil" :

All,

Thanks everyone for checking it.
I also saw, the link 2) was not working at least not in the way my email
client rendered it.
However, if there are other more severe issues, I'll wait for them to be
addressed and hope it is ready to pass very soon.

Werner



On Thu, Sep 5, 2019 at 9:35 AM Julian Feinauer 

wrote:

> Hi all,
>
> sorry for the late reply.
> I just checked the release.
>
> Sadly, I have to vote
>
> -1 (binding)
>
> as the Signatures that were used to sign the artefacts in extensions
> module are NOT in the keys file and thus cant be checked : /
>
> Furthermore, if trying to build apiandcore (as explained in README) I get
>
> Unrecognized VM option 'PermGenSpace=200m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
>
> On OS X with
> - mvn
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> - java
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> which should also be compliant due to README.
>
> If I disable PermGenSpace then I am able to build both modules
> successfully.
> So I would just delete that form the readme, than it should be fine.
> I think those issues are rather "minor" and not blocking.
>
> Furthermore I checked:
> - Signature is okay for apiandcore
> - No Hash is present (I think that’s okay?!) but it would be good to have
> sha hashes
> - NOTICE, LICENCE and DISCLAIMER look good
> - I found several files without License header (see below). Most of these
> are okay but I would check the bnd files
> - No unexpected binaries
>
> So although I have to downvote the release it looks pretty good and I
> think there are only some small changes necessary to make it pass.
>
> Julian
>
> # Appendix: Files without License header (rat output):
>
> ## Apiandcore
> 24   ./.travis.yml
>  25   ./README.md
>  26   ./maturity-model.md
> 28   ./running-mutation-tests.adoc
>  29   ./code/api/bnd.bnd
>  30   ./code/core/bnd.bnd
>  31   ./code/core/src/test/resources/java-security.policy
>  32   ./code/spi-support/bnd.bnd
>  33   ./readme/ReleaseNotes-0.1-incubating.html
>  34   ./readme/ReleaseNotes-0.2-incubating.html
>  35   ./readme/ReleaseNotes-0.3-incubating.html
>  36   ./readme/ReleaseNotes-0.4-incubating.html
>
> ## Extensions
>   24   ./.travis.yml
>   25   ./README.md
>   28   ./running-mutation-tests.adoc
>   29   ./examples/02-resolver-example/src/main/resources/build.data
>   30   ./examples/05-spring-example/README.md
>   31   ./modules/collections/bnd.bnd
>   32   ./modules/consul/bnd.bnd
>   33   ./modules/etcd/bnd.bnd
>   34   ./modules/etcd/nbactions.xml
>   35   ./modules/events/bnd.bnd
>   36   ./modules/features/bnd.bnd
>   37   ./modules/filter/bnd.bnd
>   38   ./modules/formats/base/bnd.bnd
>   39   ./modules/formats/hocon/bnd.bnd
>   40   ./modules/formats/json/bnd.bnd
>   41   ./modules/formats/yaml/bnd.bnd
>   42   ./modules/functions/bnd.bnd
>   43   ./modules/hazelcast/bnd.bnd
>   44   ./modules/injection/cdi/bnd.bnd
>   45   ./modules/injection/injection-api/bnd.bnd
>   46   ./modules/injection/standalone/bnd.bnd
>   47   ./modules/jndi/bnd.bnd
>   48   ./modules/microprofile/bnd.bnd
>   49   ./modules/mutable-config/bnd.bnd
>   50   ./modules/optional/bnd.bnd
>   51   ./modules/osgi/common/bnd.bnd
>   52   ./modules/osgi/gogo-shell/bnd.bnd
>   53   ./modules/osgi/injection/bnd.bnd
>   54   ./modules/osgi/karaf-shell/bnd.bnd
>   55   ./modules/osgi/updater/bnd.bnd
>   56   ./modules/resolver/bnd.bnd
>   57   ./modules/resources/README.md
>   58   ./modules/resources/bnd.bnd
>   59   ./modules/spring/bnd.bnd
>
>
> Am 01.09.19, 08:58 schrieb "P. Ottlinger" :
>
> Am 28.08.19 um 03:00 schrieb Anatole Tresch:
> > [ ] +1 for community members who have reviewed the bits
>
> +1
>
> I played with the core artifacts and checked the homepage changes.
>
> Did not look into much detail into sandbox and extensions, but core
> looks fine.
>
> Cheers,
> Phil
>
>
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Julian Feinauer]

Hi all,

sorry for the late reply.
I just checked the release.

Sadly, I have to vote 

-1 (binding)

as the Signatures that were used to sign the artefacts in extensions module are 
NOT in the keys file and thus cant be checked : /

Furthermore, if trying to build apiandcore (as explained in README) I get

Unrecognized VM option 'PermGenSpace=200m'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

On OS X with
- mvn
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 
2019-04-04T21:00:29+02:00)
- java
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
which should also be compliant due to README.

If I disable PermGenSpace then I am able to build both modules successfully.
So I would just delete that form the readme, than it should be fine.
I think those issues are rather "minor" and not blocking. 

Furthermore I checked:
- Signature is okay for apiandcore 
- No Hash is present (I think that’s okay?!) but it would be good to have sha 
hashes
- NOTICE, LICENCE and DISCLAIMER look good
- I found several files without License header (see below). Most of these are 
okay but I would check the bnd files
- No unexpected binaries

So although I have to downvote the release it looks pretty good and I think 
there are only some small changes necessary to make it pass.

Julian

# Appendix: Files without License header (rat output):

## Apiandcore
24   ./.travis.yml
 25   ./README.md
 26   ./maturity-model.md
28   ./running-mutation-tests.adoc
 29   ./code/api/bnd.bnd
 30   ./code/core/bnd.bnd
 31   ./code/core/src/test/resources/java-security.policy
 32   ./code/spi-support/bnd.bnd
 33   ./readme/ReleaseNotes-0.1-incubating.html
 34   ./readme/ReleaseNotes-0.2-incubating.html
 35   ./readme/ReleaseNotes-0.3-incubating.html
 36   ./readme/ReleaseNotes-0.4-incubating.html

## Extensions
  24   ./.travis.yml
  25   ./README.md
  28   ./running-mutation-tests.adoc
  29   ./examples/02-resolver-example/src/main/resources/build.data
  30   ./examples/05-spring-example/README.md
  31   ./modules/collections/bnd.bnd
  32   ./modules/consul/bnd.bnd
  33   ./modules/etcd/bnd.bnd
  34   ./modules/etcd/nbactions.xml
  35   ./modules/events/bnd.bnd
  36   ./modules/features/bnd.bnd
  37   ./modules/filter/bnd.bnd
  38   ./modules/formats/base/bnd.bnd
  39   ./modules/formats/hocon/bnd.bnd
  40   ./modules/formats/json/bnd.bnd
  41   ./modules/formats/yaml/bnd.bnd
  42   ./modules/functions/bnd.bnd
  43   ./modules/hazelcast/bnd.bnd
  44   ./modules/injection/cdi/bnd.bnd
  45   ./modules/injection/injection-api/bnd.bnd
  46   ./modules/injection/standalone/bnd.bnd
  47   ./modules/jndi/bnd.bnd
  48   ./modules/microprofile/bnd.bnd
  49   ./modules/mutable-config/bnd.bnd
  50   ./modules/optional/bnd.bnd
  51   ./modules/osgi/common/bnd.bnd
  52   ./modules/osgi/gogo-shell/bnd.bnd
  53   ./modules/osgi/injection/bnd.bnd
  54   ./modules/osgi/karaf-shell/bnd.bnd
  55   ./modules/osgi/updater/bnd.bnd
  56   ./modules/resolver/bnd.bnd
  57   ./modules/resources/README.md
  58   ./modules/resources/bnd.bnd
  59   ./modules/spring/bnd.bnd


Am 01.09.19, 08:58 schrieb "P. Ottlinger" :

Am 28.08.19 um 03:00 schrieb Anatole Tresch:
> [ ] +1 for community members who have reviewed the bits

+1

I played with the core artifacts and checked the homepage changes.

Did not look into much detail into sandbox and extensions, but core
looks fine.

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[P. Ottlinger]

Am 28.08.19 um 03:00 schrieb Anatole Tresch:
> [ ] +1 for community members who have reviewed the bits

+1

I played with the core artifacts and checked the homepage changes.

Did not look into much detail into sandbox and extensions, but core
looks fine.

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Julian Feinauer]

Thanks Anatole!
I will try to check the release later on : )

Julian

Am 28.08.19, 03:01 schrieb "Anatole Tresch" :

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache distribution repository [1] and
also via Apache's Nexus [2].

The tag for this release candidate is available at [3] and will be renamed
once the vote passed.
Please take a look at the artifacts and vote!

Please note:
This vote is a "majority approval" with a minimum of three +1 votes (see
[4]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/

[2] https://repository.apache.org/content/repositories/orgapachetamaya-103
8
[3]

https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb

[4] http://www.apache.org/foundation/voting.html#ReleaseVotes


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[VOTE] Release of Apache Tamaya 0.4-incubating-RC3

[Anatole Tresch]

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache distribution repository [1] and
also via Apache's Nexus [2].

The tag for this release candidate is available at [3] and will be renamed
once the vote passed.
Please take a look at the artifacts and vote!

Please note:
This vote is a "majority approval" with a minimum of three +1 votes (see
[4]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/

[2] https://repository.apache.org/content/repositories/orgapachetamaya-103
8
[3]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb

[4] http://www.apache.org/foundation/voting.html#ReleaseVotes


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[RESULT][VOTE] Release of Apache Tamaya 0.4-incubating, RC2

[Anatole Tresch]

This vote has been closed with no.
As mentioned earlier, we have to build a third RC due to outdated certs
used. Stay tuned...

Am Di., 27. Aug. 2019 um 20:46 Uhr schrieb Aaron Coburn <
aaron.cob...@gmail.com>:

> Thanks so much for cutting the second release candidate. The source looks
> great (no SNAPSHOT dependencies); I was able to successfully compile and
> test the code. And I was able to successfully use the CDI and Microprofile
> extensions in an external project.
>
> I'd give a +1, but there are two issues I found with the artifacts in the
> distribution area.
>
> First, I believe the .tar.gz and .zip files should have a corresponding
> sha512 checksum (there are no checksum files in
>
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/apiandcore/
>  or
>
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/extensions/
> )
>
> Second, I had some difficulty validating the signatures on the files
> themselves. I can import the KEYS file fine:
>
> $ gpg --import KEYS
>
> But the key used to sign these artifacts doesn't seem to be contained in
> that KEYS file. That is, Anatole's public key in the KEYS file has this
> signature: 2791 0BA2 1336 D3E6, but the key used to sign the files is 5B38
> A3EA FE9D 018B. I was able to find that key on a public keyserver, and it
> is registered to anat...@apache.org, but it has also been revoked:
>
> $ gpg --verify apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc
> apache-tamaya-distribution-0.4-incubating-src.tar.gz
> gpg: Signature made Mon Aug 26 18:12:12 2019 EDT
> gpg:using RSA key 754A1B93C9D5D553482A6FAE5B38A3EAFE9D018B
> gpg: Good signature from "Anatole Tresch " [unknown]
> gpg: WARNING: This key has been revoked by its owner!
> gpg:  This could mean that the signature is forged.
> gpg: reason for revocation: Key is superseded
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 754A 1B93 C9D5 D553 482A  6FAE 5B38 A3EA FE9D 018B
>
> (That key is, in fact, older than the one listed in the KEYS file)
>
> Maybe Julian can advise on whether these are blockers for a release.
>
> Cheers,
> Aaron
>
> On Tue, 27 Aug 2019 at 03:21, Anatole Tresch  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 0.4-incubating release of
> Tamaya
> > out.
> > The artifacts available via the Apache distribution repository [1] and
> > also via Apache's Nexus [2].
> >
> > The tag for this release candidate is available at [3] and will be
> renamed
> > once the vote passed.
> > Please take a look at the artifacts and vote!
> >
> > Please note:
> > This vote is a "majority approval" with a minimum of three +1 votes (see
> > [4]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why ...
> > 
> >
> > Thanks,
> > Anatole Tresch
> >
> > [1]
> > https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
> >
> > [2]
> > https://repository.apache.org/content/repositories/orgapachetamaya-1037
> > [3]
> >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
> >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com  *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating, RC2

[Anatole Tresch]

Great, another showstopper - OMG. Well why does not any tool tell me on
earth that the key on my windows account is outdated/revoked ...
Next time I build things on my Linux box ...




Am Di., 27. Aug. 2019 um 20:46 Uhr schrieb Aaron Coburn <
aaron.cob...@gmail.com>:

> Thanks so much for cutting the second release candidate. The source looks
> great (no SNAPSHOT dependencies); I was able to successfully compile and
> test the code. And I was able to successfully use the CDI and Microprofile
> extensions in an external project.
>
> I'd give a +1, but there are two issues I found with the artifacts in the
> distribution area.
>
> First, I believe the .tar.gz and .zip files should have a corresponding
> sha512 checksum (there are no checksum files in
>
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/apiandcore/
>  or
>
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/extensions/
> )
>
> Second, I had some difficulty validating the signatures on the files
> themselves. I can import the KEYS file fine:
>
> $ gpg --import KEYS
>
> But the key used to sign these artifacts doesn't seem to be contained in
> that KEYS file. That is, Anatole's public key in the KEYS file has this
> signature: 2791 0BA2 1336 D3E6, but the key used to sign the files is 5B38
> A3EA FE9D 018B. I was able to find that key on a public keyserver, and it
> is registered to anat...@apache.org, but it has also been revoked:
>
> $ gpg --verify apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc
> apache-tamaya-distribution-0.4-incubating-src.tar.gz
> gpg: Signature made Mon Aug 26 18:12:12 2019 EDT
> gpg:using RSA key 754A1B93C9D5D553482A6FAE5B38A3EAFE9D018B
> gpg: Good signature from "Anatole Tresch " [unknown]
> gpg: WARNING: This key has been revoked by its owner!
> gpg:  This could mean that the signature is forged.
> gpg: reason for revocation: Key is superseded
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 754A 1B93 C9D5 D553 482A  6FAE 5B38 A3EA FE9D 018B
>
> (That key is, in fact, older than the one listed in the KEYS file)
>
> Maybe Julian can advise on whether these are blockers for a release.
>
> Cheers,
> Aaron
>
> On Tue, 27 Aug 2019 at 03:21, Anatole Tresch  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 0.4-incubating release of
> Tamaya
> > out.
> > The artifacts available via the Apache distribution repository [1] and
> > also via Apache's Nexus [2].
> >
> > The tag for this release candidate is available at [3] and will be
> renamed
> > once the vote passed.
> > Please take a look at the artifacts and vote!
> >
> > Please note:
> > This vote is a "majority approval" with a minimum of three +1 votes (see
> > [4]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why ...
> > 
> >
> > Thanks,
> > Anatole Tresch
> >
> > [1]
> > https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
> >
> > [2]
> > https://repository.apache.org/content/repositories/orgapachetamaya-1037
> > [3]
> >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> > [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
> >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com  *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating, RC2

[P. Ottlinger]

Am 27.08.19 um 20:46 schrieb Aaron Coburn:
> (That key is, in fact, older than the one listed in the KEYS file)
> 
> Maybe Julian can advise on whether these are blockers for a release.

As the KEYS are supposed to be the way to authenticate artifacts they
should be correct .. @Anatole: can you resign the artifacts with the
correct key (that matches KEYS' contents)?

Thanks,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating, RC2

[Aaron Coburn]

Thanks so much for cutting the second release candidate. The source looks
great (no SNAPSHOT dependencies); I was able to successfully compile and
test the code. And I was able to successfully use the CDI and Microprofile
extensions in an external project.

I'd give a +1, but there are two issues I found with the artifacts in the
distribution area.

First, I believe the .tar.gz and .zip files should have a corresponding
sha512 checksum (there are no checksum files in
https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/apiandcore/
 or
https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/extensions/
)

Second, I had some difficulty validating the signatures on the files
themselves. I can import the KEYS file fine:

$ gpg --import KEYS

But the key used to sign these artifacts doesn't seem to be contained in
that KEYS file. That is, Anatole's public key in the KEYS file has this
signature: 2791 0BA2 1336 D3E6, but the key used to sign the files is 5B38
A3EA FE9D 018B. I was able to find that key on a public keyserver, and it
is registered to anat...@apache.org, but it has also been revoked:

$ gpg --verify apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc
apache-tamaya-distribution-0.4-incubating-src.tar.gz
gpg: Signature made Mon Aug 26 18:12:12 2019 EDT
gpg:using RSA key 754A1B93C9D5D553482A6FAE5B38A3EAFE9D018B
gpg: Good signature from "Anatole Tresch " [unknown]
gpg: WARNING: This key has been revoked by its owner!
gpg:  This could mean that the signature is forged.
gpg: reason for revocation: Key is superseded
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 754A 1B93 C9D5 D553 482A  6FAE 5B38 A3EA FE9D 018B

(That key is, in fact, older than the one listed in the KEYS file)

Maybe Julian can advise on whether these are blockers for a release.

Cheers,
Aaron

On Tue, 27 Aug 2019 at 03:21, Anatole Tresch  wrote:

> Hi,
>
> I was running the needed tasks to get the 0.4-incubating release of Tamaya
> out.
> The artifacts available via the Apache distribution repository [1] and
> also via Apache's Nexus [2].
>
> The tag for this release candidate is available at [3] and will be renamed
> once the vote passed.
> Please take a look at the artifacts and vote!
>
> Please note:
> This vote is a "majority approval" with a minimum of three +1 votes (see
> [4]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be released, and
> why ...
> 
>
> Thanks,
> Anatole Tresch
>
> [1]
> https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/
>
> [2]
> https://repository.apache.org/content/repositories/orgapachetamaya-1037
> [3]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
>
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com  *
> *Twitter:  @atsticks, @tamayaconf*
>

[VOTE] Release of Apache Tamaya 0.4-incubating, RC2

[Anatole Tresch]

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache distribution repository [1] and
also via Apache's Nexus [2].

The tag for this release candidate is available at [3] and will be renamed
once the vote passed.
Please take a look at the artifacts and vote!

Please note:
This vote is a "majority approval" with a minimum of three +1 votes (see
[4]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.4-incubating/

[2] https://repository.apache.org/content/repositories/orgapachetamaya-1037
[3]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
[4] http://www.apache.org/foundation/voting.html#ReleaseVotes



-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[RESULT][VOTE] Release of Apache Tamaya 0.4-incubating

[Anatole Tresch]

This vote has been closed since there were SNAPSHOT references in some POM
files.
So I will recreate the release after this has been fixed and restart a new
vote (already happened).

J Anatole

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

[VOTE] Release of Apache Tamaya 0.4-incubating - Vote 02

[Anatole Tresch]

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache's Nexus [1].
The tag for this release candidate is available at [2] and will be renamed
once the vote passed.

Please take a look at the artifacts and vote!

Please note: This vote is a "majority approval" with a minimum of three +1
votes (see [3]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://repository.apache.org/content/repositories/orgapachetamaya-103
7/
[2]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
[3] http://www.apache.org/foundation/voting.html#ReleaseVotes

-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Anatole Tresch]

Aaron, thanks very much for these points. The sandbox is not an issue since
it is not part of the release. It can be updated after the release
separately.

Am Mo., 26. Aug. 2019 um 17:37 Uhr schrieb Aaron Coburn <
aaron.cob...@gmail.com>:

> -1 (non-binding)
>
> The microprofile extension depends on the tamaya-api
> 0.4-incubating-SNAPSHOT artifact, which will cause problems when trying to
> use that (and that is the artifact I am most interested in using)
>
>
> https://github.com/apache/incubator-tamaya-extensions/blob/vote-0.4-incubating-01/modules/microprofile/pom.xml#L39
>
> In the sandbox modules, it appears that most (all?) of the modules depend
> on SNAPSHOT artifacts from tamaya-api and various -extension artifacts:
>
> https://github.com/apache/incubator-tamaya-sandbox/blob/vote-0.4-incubating-01/pom.xml#L43
>
> Less significant: examples 05 and 06 in the extension repo also depend on
> snapshot artifacts.
>
> Otherwise, the code builds and tests correctly.
>
> Aaron
>
>
>
> On Sun, 25 Aug 2019 at 11:42, Anatole Tresch  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 0.4-incubating release of
> Tamaya
> > out.
> > The artifacts available via the Apache's Nexus [1].
> > The tag for this release candidate is available at [2] and will be
> renamed
> > once the vote passed.
> >
> > Please take a look at the artifacts and vote!
> >
> > Please note: This vote is a "majority approval" with a minimum of three
> +1
> > votes (see [3]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why ...
> > 
> >
> > Thanks,
> > Anatole Tresch
> >
> > [1]
> > https://repository.apache.org/content/repositories/orgapachetamaya-1036/
> >
> > [2]
> >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> >
> > [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com  *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[P. Ottlinger]

Thanks for your efforts, Anatole!

Am 26.08.19 um 19:22 schrieb Anatole Tresch:
> its rather simple. We have to fix it, and rebuild everything. Takes round
> about ab hour, so I try to do so later.

+1

We must not depend on SNAPSHOTs.

Apart from that the vote thread should have a definite end 

My pet project - only depending on tamaya-core - worked fine so far.

Cheers,
Phil

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Anatole Tresch]

its rather simple. We have to fix it, and rebuild everything. Takes round
about ab hour, so I try to do so later.

J Anatole

Werner Keil  schrieb am Mo., 26. Aug. 2019, 19:06:

> Could you point us/Anatole to how it can be addressed?
>
> Thanks,
>
> Werner
>
>
>
>
> On Mon, Aug 26, 2019 at 6:08 PM Aaron Coburn 
> wrote:
>
> > The staging repository should be exactly the same as the eventual
> released
> > artifacts. You can see in the POM file for the microprofile artifact that
> > it depends on a SNAPSHOT API:
> >
> >
> https://repository.apache.org/content/repositories/orgapachetamaya-1036/org/apache/tamaya/ext/tamaya-microprofile/0.4-incubating/tamaya-microprofile-0.4-incubating.pom
> >
> > If released as-is, the microprofile artifact will not work properly. (The
> > same applies to the -sandbox items)
> >
> >
> >
> >
> > On Mon, 26 Aug 2019 at 11:43, Werner Keil  wrote:
> >
> > > Wouldn't it be possible to change from snapshot only once 0.4 is
> > released,
> > > or should it work without Snapshot in staging?
> > >
> > > Aaron Coburn  schrieb am Mo., 26. Aug. 2019,
> > > 17:37:
> > >
> > > > -1 (non-binding)
> > > >
> > > > The microprofile extension depends on the tamaya-api
> > > > 0.4-incubating-SNAPSHOT artifact, which will cause problems when
> trying
> > > to
> > > > use that (and that is the artifact I am most interested in using)
> > > >
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-tamaya-extensions/blob/vote-0.4-incubating-01/modules/microprofile/pom.xml#L39
> > > >
> > > > In the sandbox modules, it appears that most (all?) of the modules
> > depend
> > > > on SNAPSHOT artifacts from tamaya-api and various -extension
> artifacts:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-tamaya-sandbox/blob/vote-0.4-incubating-01/pom.xml#L43
> > > >
> > > > Less significant: examples 05 and 06 in the extension repo also
> depend
> > on
> > > > snapshot artifacts.
> > > >
> > > > Otherwise, the code builds and tests correctly.
> > > >
> > > > Aaron
> > > >
> > > >
> > > >
> > > > On Sun, 25 Aug 2019 at 11:42, Anatole Tresch 
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I was running the needed tasks to get the 0.4-incubating release of
> > > > Tamaya
> > > > > out.
> > > > > The artifacts available via the Apache's Nexus [1].
> > > > > The tag for this release candidate is available at [2] and will be
> > > > renamed
> > > > > once the vote passed.
> > > > >
> > > > > Please take a look at the artifacts and vote!
> > > > >
> > > > > Please note: This vote is a "majority approval" with a minimum of
> > three
> > > > +1
> > > > > votes (see [3]).
> > > > >
> > > > > 
> > > > > [ ] +1 for community members who have reviewed the bits
> > > > > [ ] +0
> > > > > [ ] -1 for fatal flaws that should cause these bits not to be
> > released,
> > > > and
> > > > > why ...
> > > > > 
> > > > >
> > > > > Thanks,
> > > > > Anatole Tresch
> > > > >
> > > > > [1]
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachetamaya-1036/
> > > > >
> > > > > [2]
> > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> > > > >
> > > > > [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
> > > > >
> > > > >
> > > > > --
> > > > > *Anatole Tresch*
> > > > > PPMC Member Apache Tamaya
> > > > > JCP Star Spec Lead
> > > > > *Switzerland, Europe Zurich, GMT+1*
> > > > > *maketechsimple.wordpress.com <
> http://maketechsimple.wordpress.com/>
> > *
> > > > > *Twitter:  @atsticks, @tamayaconf*
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Werner Keil]

Could you point us/Anatole to how it can be addressed?

Thanks,

Werner




On Mon, Aug 26, 2019 at 6:08 PM Aaron Coburn  wrote:

> The staging repository should be exactly the same as the eventual released
> artifacts. You can see in the POM file for the microprofile artifact that
> it depends on a SNAPSHOT API:
>
> https://repository.apache.org/content/repositories/orgapachetamaya-1036/org/apache/tamaya/ext/tamaya-microprofile/0.4-incubating/tamaya-microprofile-0.4-incubating.pom
>
> If released as-is, the microprofile artifact will not work properly. (The
> same applies to the -sandbox items)
>
>
>
>
> On Mon, 26 Aug 2019 at 11:43, Werner Keil  wrote:
>
> > Wouldn't it be possible to change from snapshot only once 0.4 is
> released,
> > or should it work without Snapshot in staging?
> >
> > Aaron Coburn  schrieb am Mo., 26. Aug. 2019,
> > 17:37:
> >
> > > -1 (non-binding)
> > >
> > > The microprofile extension depends on the tamaya-api
> > > 0.4-incubating-SNAPSHOT artifact, which will cause problems when trying
> > to
> > > use that (and that is the artifact I am most interested in using)
> > >
> > >
> > >
> >
> https://github.com/apache/incubator-tamaya-extensions/blob/vote-0.4-incubating-01/modules/microprofile/pom.xml#L39
> > >
> > > In the sandbox modules, it appears that most (all?) of the modules
> depend
> > > on SNAPSHOT artifacts from tamaya-api and various -extension artifacts:
> > >
> > >
> >
> https://github.com/apache/incubator-tamaya-sandbox/blob/vote-0.4-incubating-01/pom.xml#L43
> > >
> > > Less significant: examples 05 and 06 in the extension repo also depend
> on
> > > snapshot artifacts.
> > >
> > > Otherwise, the code builds and tests correctly.
> > >
> > > Aaron
> > >
> > >
> > >
> > > On Sun, 25 Aug 2019 at 11:42, Anatole Tresch 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > I was running the needed tasks to get the 0.4-incubating release of
> > > Tamaya
> > > > out.
> > > > The artifacts available via the Apache's Nexus [1].
> > > > The tag for this release candidate is available at [2] and will be
> > > renamed
> > > > once the vote passed.
> > > >
> > > > Please take a look at the artifacts and vote!
> > > >
> > > > Please note: This vote is a "majority approval" with a minimum of
> three
> > > +1
> > > > votes (see [3]).
> > > >
> > > > 
> > > > [ ] +1 for community members who have reviewed the bits
> > > > [ ] +0
> > > > [ ] -1 for fatal flaws that should cause these bits not to be
> released,
> > > and
> > > > why ...
> > > > 
> > > >
> > > > Thanks,
> > > > Anatole Tresch
> > > >
> > > > [1]
> > > >
> > https://repository.apache.org/content/repositories/orgapachetamaya-1036/
> > > >
> > > > [2]
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> > > >
> > > > [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
> > > >
> > > >
> > > > --
> > > > *Anatole Tresch*
> > > > PPMC Member Apache Tamaya
> > > > JCP Star Spec Lead
> > > > *Switzerland, Europe Zurich, GMT+1*
> > > > *maketechsimple.wordpress.com 
> *
> > > > *Twitter:  @atsticks, @tamayaconf*
> > > >
> > >
> >
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Aaron Coburn]

The staging repository should be exactly the same as the eventual released
artifacts. You can see in the POM file for the microprofile artifact that
it depends on a SNAPSHOT API:
https://repository.apache.org/content/repositories/orgapachetamaya-1036/org/apache/tamaya/ext/tamaya-microprofile/0.4-incubating/tamaya-microprofile-0.4-incubating.pom

If released as-is, the microprofile artifact will not work properly. (The
same applies to the -sandbox items)




On Mon, 26 Aug 2019 at 11:43, Werner Keil  wrote:

> Wouldn't it be possible to change from snapshot only once 0.4 is released,
> or should it work without Snapshot in staging?
>
> Aaron Coburn  schrieb am Mo., 26. Aug. 2019,
> 17:37:
>
> > -1 (non-binding)
> >
> > The microprofile extension depends on the tamaya-api
> > 0.4-incubating-SNAPSHOT artifact, which will cause problems when trying
> to
> > use that (and that is the artifact I am most interested in using)
> >
> >
> >
> https://github.com/apache/incubator-tamaya-extensions/blob/vote-0.4-incubating-01/modules/microprofile/pom.xml#L39
> >
> > In the sandbox modules, it appears that most (all?) of the modules depend
> > on SNAPSHOT artifacts from tamaya-api and various -extension artifacts:
> >
> >
> https://github.com/apache/incubator-tamaya-sandbox/blob/vote-0.4-incubating-01/pom.xml#L43
> >
> > Less significant: examples 05 and 06 in the extension repo also depend on
> > snapshot artifacts.
> >
> > Otherwise, the code builds and tests correctly.
> >
> > Aaron
> >
> >
> >
> > On Sun, 25 Aug 2019 at 11:42, Anatole Tresch  wrote:
> >
> > > Hi,
> > >
> > > I was running the needed tasks to get the 0.4-incubating release of
> > Tamaya
> > > out.
> > > The artifacts available via the Apache's Nexus [1].
> > > The tag for this release candidate is available at [2] and will be
> > renamed
> > > once the vote passed.
> > >
> > > Please take a look at the artifacts and vote!
> > >
> > > Please note: This vote is a "majority approval" with a minimum of three
> > +1
> > > votes (see [3]).
> > >
> > > 
> > > [ ] +1 for community members who have reviewed the bits
> > > [ ] +0
> > > [ ] -1 for fatal flaws that should cause these bits not to be released,
> > and
> > > why ...
> > > 
> > >
> > > Thanks,
> > > Anatole Tresch
> > >
> > > [1]
> > >
> https://repository.apache.org/content/repositories/orgapachetamaya-1036/
> > >
> > > [2]
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> > >
> > > [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
> > >
> > >
> > > --
> > > *Anatole Tresch*
> > > PPMC Member Apache Tamaya
> > > JCP Star Spec Lead
> > > *Switzerland, Europe Zurich, GMT+1*
> > > *maketechsimple.wordpress.com  *
> > > *Twitter:  @atsticks, @tamayaconf*
> > >
> >
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Werner Keil]

Wouldn't it be possible to change from snapshot only once 0.4 is released,
or should it work without Snapshot in staging?

Aaron Coburn  schrieb am Mo., 26. Aug. 2019, 17:37:

> -1 (non-binding)
>
> The microprofile extension depends on the tamaya-api
> 0.4-incubating-SNAPSHOT artifact, which will cause problems when trying to
> use that (and that is the artifact I am most interested in using)
>
>
> https://github.com/apache/incubator-tamaya-extensions/blob/vote-0.4-incubating-01/modules/microprofile/pom.xml#L39
>
> In the sandbox modules, it appears that most (all?) of the modules depend
> on SNAPSHOT artifacts from tamaya-api and various -extension artifacts:
>
> https://github.com/apache/incubator-tamaya-sandbox/blob/vote-0.4-incubating-01/pom.xml#L43
>
> Less significant: examples 05 and 06 in the extension repo also depend on
> snapshot artifacts.
>
> Otherwise, the code builds and tests correctly.
>
> Aaron
>
>
>
> On Sun, 25 Aug 2019 at 11:42, Anatole Tresch  wrote:
>
> > Hi,
> >
> > I was running the needed tasks to get the 0.4-incubating release of
> Tamaya
> > out.
> > The artifacts available via the Apache's Nexus [1].
> > The tag for this release candidate is available at [2] and will be
> renamed
> > once the vote passed.
> >
> > Please take a look at the artifacts and vote!
> >
> > Please note: This vote is a "majority approval" with a minimum of three
> +1
> > votes (see [3]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why ...
> > 
> >
> > Thanks,
> > Anatole Tresch
> >
> > [1]
> > https://repository.apache.org/content/repositories/orgapachetamaya-1036/
> >
> > [2]
> >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
> >
> > [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
> >
> > --
> > *Anatole Tresch*
> > PPMC Member Apache Tamaya
> > JCP Star Spec Lead
> > *Switzerland, Europe Zurich, GMT+1*
> > *maketechsimple.wordpress.com  *
> > *Twitter:  @atsticks, @tamayaconf*
> >
>

Re: [VOTE] Release of Apache Tamaya 0.4-incubating

[Aaron Coburn]

-1 (non-binding)

The microprofile extension depends on the tamaya-api
0.4-incubating-SNAPSHOT artifact, which will cause problems when trying to
use that (and that is the artifact I am most interested in using)

https://github.com/apache/incubator-tamaya-extensions/blob/vote-0.4-incubating-01/modules/microprofile/pom.xml#L39

In the sandbox modules, it appears that most (all?) of the modules depend
on SNAPSHOT artifacts from tamaya-api and various -extension artifacts:
https://github.com/apache/incubator-tamaya-sandbox/blob/vote-0.4-incubating-01/pom.xml#L43

Less significant: examples 05 and 06 in the extension repo also depend on
snapshot artifacts.

Otherwise, the code builds and tests correctly.

Aaron



On Sun, 25 Aug 2019 at 11:42, Anatole Tresch  wrote:

> Hi,
>
> I was running the needed tasks to get the 0.4-incubating release of Tamaya
> out.
> The artifacts available via the Apache's Nexus [1].
> The tag for this release candidate is available at [2] and will be renamed
> once the vote passed.
>
> Please take a look at the artifacts and vote!
>
> Please note: This vote is a "majority approval" with a minimum of three +1
> votes (see [3]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be released, and
> why ...
> 
>
> Thanks,
> Anatole Tresch
>
> [1]
> https://repository.apache.org/content/repositories/orgapachetamaya-1036/
>
> [2]
>
> https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb
>
> [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com  *
> *Twitter:  @atsticks, @tamayaconf*
>

[VOTE] Release of Apache Tamaya 0.4-incubating

[Anatole Tresch]

Hi,

I was running the needed tasks to get the 0.4-incubating release of Tamaya
out.
The artifacts available via the Apache's Nexus [1].
The tag for this release candidate is available at [2] and will be renamed
once the vote passed.

Please take a look at the artifacts and vote!

Please note: This vote is a "majority approval" with a minimum of three +1
votes (see [3]).


[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, and
why ...


Thanks,
Anatole Tresch

[1] https://repository.apache.org/content/repositories/orgapachetamaya-1036/

[2]
https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;a=commit;h=d2d60786e3e72a2bb16e14e1b195f7b2487a33eb

[3] http://www.apache.org/foundation/voting.html#ReleaseVotes


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com  *
*Twitter:  @atsticks, @tamayaconf*