[BUILD-STABLE]: Job 'PLC4X/PLC4X/develop [develop] [190]'

2019-01-24 Thread Apache Jenkins Server
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [190]': Is back to normal.

Re: [VOTE] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Justin Mclean
Hi, A -1 vote on a release is not a veto, you should wait and see what other PPMC members think, you can also try and convince the person to change their vote. Thanks, Justin

Re: [DISCUSS] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Justin Mclean
Hi, > I just checked the RELEASE_NOTES and saw that I never changed the > "(Unreleased) 0.3.0". > Is this a problem for the release and does this justify -1 vote? No a hug issue IMO, just fix it in the next release. Thanks, Justin

[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [189]'

2019-01-24 Thread Apache Jenkins Server
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [189]': Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/189/";>PLC4X/PLC4X/develop [develop] [189]"

[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [188]'

2019-01-24 Thread Apache Jenkins Server
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [188]': Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/188/";>PLC4X/PLC4X/develop [develop] [188]"

Re: [VOTE] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Julian Feinauer
Hi Chris, thanks for your feedback. So I'll close the vote here and prepare an rc2 and start a new vote than. Best! Julian Am 24.01.19, 15:40 schrieb "Christofer Dutz" : -1 (binding) chris The RELEASE_NOTES don't reference the proper release version and it contains the prefix "(U

Re: [VOTE] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Christofer Dutz
-1 (binding) chris The RELEASE_NOTES don't reference the proper release version and it contains the prefix "(Unreleased)". Besides this, I did the full check: - tools/download_staged_release.sh 0.3.0 1 (Downloaded and verified, after I removed the download of MD5 which we removed in the last re

[DISCUSS] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Julian Feinauer
This is the discussion thread for the corresponding VOTE thread. Please keep discussions in this thread to simplify the counting of votes. If you have to vote -1 please mention a brief description on why and then take the details to this thread. Julian

Re: [DISCUSS] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Julian Feinauer
Hi all, I just checked the RELEASE_NOTES and saw that I never changed the "(Unreleased) 0.3.0". Is this a problem for the release and does this justify -1 vote? Are there any (written-down) rules for that? Julian Am 24.01.19, 14:47 schrieb "Julian Feinauer" : This is the discussion thread

Re: [DISCUSS] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Christofer Dutz
Yup ... just wanted to report that too ... Chris Am 24.01.19, 14:54 schrieb "Julian Feinauer" : Hi all, I just checked the RELEASE_NOTES and saw that I never changed the "(Unreleased) 0.3.0". Is this a problem for the release and does this justify -1 vote? Are there any (

Re: [DISCUSS] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Christofer Dutz
But I would let us finish the check, if we are to find anything else ... Chris Am 24.01.19, 15:02 schrieb "Otto Fowler" : I think you should fail with a -1 and cut a new RC with the right notes. On January 24, 2019 at 08:54:18, Julian Feinauer ( j.feina...@pragmaticminds.d

Re: [DISCUSS] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Otto Fowler
I think you should fail with a -1 and cut a new RC with the right notes. On January 24, 2019 at 08:54:18, Julian Feinauer ( j.feina...@pragmaticminds.de) wrote: Hi all, I just checked the RELEASE_NOTES and saw that I never changed the "(Unreleased) 0.3.0". Is this a problem for the release and

[VOTE] Apache PLC4X (Incubating) 0.3.0 RC1

2019-01-24 Thread Julian Feinauer
Apache PLC4X (Incubating) 0.3.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. If approved we will seek final release approval from the IPMC. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +