Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

[Paul King]

+1 (binding) with some caveats.

I checked:
* Incubating in name
* DISCLAIMER exists
* LICENSE and NOTICE okay (copyright end year in NOTICE needs a bump I
would suspect)
* Signatures okay
* Checksums okay

My understanding is that the KEYS file for your project is expected in:
  https://dist.apache.org/repos/dist/release/incubator/samoa/KEYS (or via
the external URL https://downloads.apache.org/incubator/samoa/KEYS)
It would normally contain the keys for all release managers. I believe you
can just copy your file there now - please do.

Rat indicates that the following files need headers or an exclusion (if
generated or header can't be there for some technical reason):
  sign.sh
  DEPENDENCIES
  CONTRIBUTING.md
  checkstyle/header.regexp
  bin/samza-kryo
  src/main/resources/kafka.avsc (samoa-api)
  src/main/resources/META-INF/services/org.apache.hadoop.fs.FileSystem
(samoa-api)
[None of these seem like critical IP to me, so not worth cancelling but
this should be easy to fix up for next release.]

The following test failed on Ubuntu and WSL:
  Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.384 sec
<<< FAILURE! - in
org.apache.samoa.topology.impl.SimpleEntranceProcessingItemTest

testStartSendingEvents(org.apache.samoa.topology.impl.SimpleEntranceProcessingItemTest)
 Time elapsed: 0.31 sec  <<< ERROR!
  java.lang.IllegalStateException: Missing invocation to mocked type at
this point; please make sure there is an associated mock field or mock
parameter in scope
  at
org.apache.samoa.topology.impl.SimpleEntranceProcessingItemTest$4.(SimpleEntranceProcessingItemTest.java:158)...

Additional tests failed under Windows, e.g.:
  Tests run: 10, Failures: 0, Errors: 10, Skipped: 0, Time elapsed: 8.097
sec <<< FAILURE! - in org.apache.samoa.streams.fs.HDFSFileStreamSourceTest

testGetNextInputStream(org.apache.samoa.streams.fs.HDFSFileStreamSourceTest)
 Time elapsed: 6.661 sec  <<< ERROR!
  java.lang.UnsatisfiedLinkError:
org.apache.hadoop.io.nativeio.NativeIO$Windows.access0(Ljava/lang/String;I)Z...

Attempting to test under Windows with JDK 11.0.5 gave:
  [ERROR] Caused by: java.lang.IllegalStateException: JMockit requires a
Java 6+ VM
  [ERROR] at
mockit.internal.startup.AgentInitialization.loadAgentFromLocalJarFile(AgentInitialization.java:25)
[I am assuming there is something I don't have set up correctly in my
environment but would be good for you to list recommended JDK
versions/platforms in your vote email (and release email) if there are
restrictions, or point to some doco where such info is available]

I could build from source using `mvn -Dmaven.test.skip=true package` and
was then able to run the classifiers.ensemble.Bagging example from the
project home page.
[After printing out what looked like the results, bin/samoa didn't return
to the command prompt. I didn't know if that is expected behavior.]

Cheers, Paul.



On Mon, Mar 16, 2020 at 7:40 AM Corey Sterling 
wrote:

> Hi all,
>
> The SAMOA community has voted to promote a release candidate to a
> full-release.
>
> The vote thread can be found at:
>
> https://lists.apache.org/thread.html/r9ee34c67da99269915485635ae9c86e158fb9e149727e699d3990e23%40%3Cdev.samoa.apache.org%3E
>
> and the result thread at:
>
> https://lists.apache.org/thread.html/r066a4c6334e155887f6ab199fb9f52e0b7798a9a1940cae69a29671d%40%3Cdev.samoa.apache.org%3E
>
> We now invite the general incubator community to vote on releasing the same
> release candidate as Apache SAMOA (incubating) version 0.5.0.
>
> Release candidate 2 was skipped as during it's creation the Github mirror
> of the branch became out-of-sync with the Apache source repository.
>
> This release will be the third release for SAMOA in the incubator.
>
> -
> The commit to be voted on is in the branch "releases/0.5.0-incubating-RC3"
> (commit 9fe3b5582b7c697a00151902bd7e945aaf07506f):
> https://git-wip-us.apache.org/repos/asf?p=incubator-samoa
> .git;a=commit;h=9fe3b5582b7c697a00151902bd7e945aaf07506f
>
> Tag v0.5.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-samoa
> .git;a=commit;h=856a16920f7c19f94c43c3cdd287a86f52087c15
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/csterling
>
> The staging repository for this release can be found at:
>
> https://repository.apache.org/content/repositories/staging/org/apache/samoa/
> samoa/0.5.0-incubating/
> 
>
> The developer's version artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/samoa/0.5.0-incubating-rc3/
>
> -
>
> Please vote on releasing this package as Apache SAMOA 0.5.0 (incubating).
>
> [ ] +1 Release this package as Apache SAMOA 0.5.0 (incubating)
> [ ] -1 Do not release this package because ...
>
> Cheers,
>
> Corey.
>

Re: [VOTE] Graduate Apache ShardingSphere (incubating)

[tan zhongyi]

+1

Best wishes.



在 2020/3/15 上午8:40，“ShaoFeng Shi” 写入:

+1 (binding), Gook luck!

Best regards,

Shaofeng Shi 史少锋
Apache Kylin PMC
Email: shaofeng...@apache.org

Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: user-subscr...@kylin.apache.org
Join Kylin dev mail group: dev-subscr...@kylin.apache.org




Liang Chen  于2020年3月14日周六 下午4:59写道：

> +1(binding)
>
> Regards
> Liang
>
>
>
> --
> Sent from: http://apache-incubator-general.996316.n3.nabble.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Hudi (incubating) 0.5.2 RC1

[Suneel Marthi]

transferring my vote from dev@hudi

+1 binding



On Sun, Mar 15, 2020 at 10:58 PM vino yang  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
> Deletes and Incrementals. Apache Hudi (incubating) manages storage of
> large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
> FileSystem compatible storage) and provide ability to query them.
>
> The Apache Hudi (incubating) community has voted on the release candidate
> and approved. The new source release candidate version is
> 0.5.2-incubating-rc1
>
> Results: 6 binding +1 votes
>
> Here is the voting
> thread:
> https://lists.apache.org/thread.html/rf687b44fb8d5e9073c2918a0c366352379ddf01632832adcbfcc060e%40%3Cdev.hudi.apache.org%3E
>
> Here is the voting result
> email:
> https://lists.apache.org/thread.html/rfaad30944d931d07c7a3f8b143b810891d9d80ad61fc6a1f5b7c0dcf%40%3Cdev.hudi.apache.org%3E
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the release of Apache Hudi
> (incubating). Please review and vote on the release candidate #1 for the
> version 0.5.2, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-0.5.2-incubating-rc1" [5],
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822=12346606
>
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc1/
>
> [3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>
> [4] https://repository.apache.org/content/repositories/orgapachehudi-1018/
>
> [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc1
>
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.2 --rc_num=1
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> Best,
>
> vino
>

[VOTE] Apache Hudi (incubating) 0.5.2 RC1

[vino yang]

Dear IPMC,

Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
Deletes and Incrementals. Apache Hudi (incubating) manages storage of
large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
FileSystem compatible storage) and provide ability to query them.

The Apache Hudi (incubating) community has voted on the release candidate
and approved. The new source release candidate version is 0.5.2-incubating-rc1

Results: 6 binding +1 votes

Here is the voting
thread:https://lists.apache.org/thread.html/rf687b44fb8d5e9073c2918a0c366352379ddf01632832adcbfcc060e%40%3Cdev.hudi.apache.org%3E

Here is the voting result
email:https://lists.apache.org/thread.html/rfaad30944d931d07c7a3f8b143b810891d9d80ad61fc6a1f5b7c0dcf%40%3Cdev.hudi.apache.org%3E

The Apache Hudi community had verified the following aspects of release:
- verified checksums and signatures [SUCCESS]
- license header check [SUCCESS]
- No binaries in source release [SUCCESS]
- verified RAT check [SUCCESS]
- built from source release (mvn clean install -DskipTests) [SUCCESS]
- mvn test from source release [SUCCESS]

I'd like to call a vote in general to approve the release of Apache Hudi
(incubating). Please review and vote on the release candidate #1 for the
version 0.5.2, as follows:
[ ] +1,  Approve the release
[ ]  0,  I don't feel strongly about it, but I'm okay with the release
[ ] -1,  Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-0.5.2-incubating-rc1" [5],

[1] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822=12346606

[2] 
https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc1/

[3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS

[4] https://repository.apache.org/content/repositories/orgapachehudi-1018/

[5] https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc1


A release validation script is available in master for running usual
checks. To run this

  - git clone g...@github.com:apache/incubator-hudi.git
  - cd incubator-hudi/scripts
  - ./release/validate_staged_release.sh --release=0.5.2 --rc_num=1

The vote will be open for at least 72 hours. The vote will pass if a
majority of at least three +1 IPMC votes are cast.

Best,

vino

[VOTE] Release SAMOA 0.5.0 (incubating) RC3

[Corey Sterling]

Hi all,

The SAMOA community has voted to promote a release candidate to a
full-release.

The vote thread can be found at:
https://lists.apache.org/thread.html/r9ee34c67da99269915485635ae9c86e158fb9e149727e699d3990e23%40%3Cdev.samoa.apache.org%3E

and the result thread at:
https://lists.apache.org/thread.html/r066a4c6334e155887f6ab199fb9f52e0b7798a9a1940cae69a29671d%40%3Cdev.samoa.apache.org%3E

We now invite the general incubator community to vote on releasing the same
release candidate as Apache SAMOA (incubating) version 0.5.0.

Release candidate 2 was skipped as during it's creation the Github mirror
of the branch became out-of-sync with the Apache source repository.

This release will be the third release for SAMOA in the incubator.

-
The commit to be voted on is in the branch "releases/0.5.0-incubating-RC3"
(commit 9fe3b5582b7c697a00151902bd7e945aaf07506f):
https://git-wip-us.apache.org/repos/asf?p=incubator-samoa
.git;a=commit;h=9fe3b5582b7c697a00151902bd7e945aaf07506f

Tag v0.5.0-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-samoa
.git;a=commit;h=856a16920f7c19f94c43c3cdd287a86f52087c15

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/csterling

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/staging/org/apache/samoa/
samoa/0.5.0-incubating/

The developer's version artifacts:
https://dist.apache.org/repos/dist/dev/incubator/samoa/0.5.0-incubating-rc3/

-

Please vote on releasing this package as Apache SAMOA 0.5.0 (incubating).

[ ] +1 Release this package as Apache SAMOA 0.5.0 (incubating)
[ ] -1 Do not release this package because ...

Cheers,

Corey.

Re: [VOTE] Release Apache Annotator (incubating) 0.1.0 (-rc.2)

[Justin Mclean]

Hi,

> Do you have a link that explains more about where to put what for LICENSE and 
> NOTICE?

Yep [1].

> From what I'd understood LICENSE was to remain the pure Apache License 2.0 
> text and NOTICE should contain any reference to any other copywritten 
> material contained within the repo--though it seems we missed bringing in the 
> complete license text either place. Happy to correct this once I understand 
> which thing is needed.

You need to add all licences to LICENSE. The only copyright notices that go in 
NOTICE are those that have been removed from headers or those that appear in 
other NOTICE files.

> Also when you say "incubating in name" what is the context (and is that a 
> positive or negative comment)?

That’s a requirement. [2] You might want to make a check list like this one [3] 
to check future releases.

> Also, what binary files did you find in the release?

None - that’s good.

You might also want to use the work in progress DISCLAIMER [4]

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html
2. https://incubator.apache.org/policy/incubation.html#releases 
3. 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
4. https://incubator.apache.org/policy/incubation.html#disclaimers
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release Apache Annotator (incubating) 0.1.0 (-rc.2)

[Benjamin Young]

Thanks, Justin!

Do you have a link that explains more about where to put what for LICENSE and 
NOTICE?

>From what I'd understood LICENSE was to remain the pure Apache License 2.0 
>text and NOTICE should contain any reference to any other copywritten material 
>contained within the repo--though it seems we missed bringing in the complete 
>license text either place. Happy to correct this once I understand which thing 
>is needed.

Also when you say "incubating in name" what is the context (and is that a 
positive or negative comment)?

Also, what binary files did you find in the release?

Thanks!
Benjamin

-Original Message-
From: Justin Mclean  
Sent: Sunday, March 15, 2020 4:03 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache Annotator (incubating) 0.1.0 (-rc.2)

Hi,

-1 (binding) as LICENSE issues mentioned on the last RC have not been fixed and 
this release is not using the work in progress disclaimer.

I  checked:
- incubating in name
- LICENSE is missing 3rd party license information and full text of licenses is 
not include
- NOTICE incorrectly mentions licenses
- No binary files in release
- This file is missing an ASF header [1]. although it may come from here [2] 
and if so needs to be mentioned in LICENSE. (Note running Apache Rat on this 
release shows that issue.)
- Can compile from source

Thanks,
Justin


1.  apache-annotator-0.1.0-incubating/packages/dom/src/highlight-range.js
2. https://github.com/Treora/dom-highlight-range
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Tuweni 1.0.0-incubating release

[Paul King]

I had the same questions Justin mentioned wrt  gossip and relayer but
forgot to mention that.
One approach could be to have your artifacts split into sources and
distributions subdirectories (or similar names).

Cheers, Paul.

On Sun, Mar 15, 2020 at 5:37 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked only the source release:
> - incubating in name
> - signature and hashes good
> - DISCLAIMER exists
> - LICENSE and NOTICE are good
> - No unexpected binary files
> - Hard to tell if any files are missing headers due to large number of
> Json files
> - Didn’t compile from source
>
> It a little unclear from the names if if gossip and relayer are binary or
> source artefacts, you might want to correct that.
>
> Also you might want consider  removing the large amount of test resource
> form the source release, IMO users generally want to build the release not
> test it ands it on the rather large size with some test file being over 1Mb.
>
> Thanks,
> Justin
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Annotator (incubating) 0.1.0 (-rc.2)

[Justin Mclean]

Hi,

-1 (binding) as LICENSE issues mentioned on the last RC have not been fixed and 
this release is not using the work in progress disclaimer.

I  checked:
- incubating in name
- LICENSE is missing 3rd party license information and full text of licenses is 
not include
- NOTICE incorrectly mentions licenses
- No binary files in release
- This file is missing an ASF header [1]. although it may come from here [2] 
and if so needs to be mentioned in LICENSE. (Note running Apache Rat on this 
release shows that issue.)
- Can compile from source

Thanks,
Justin


1.  apache-annotator-0.1.0-incubating/packages/dom/src/highlight-range.js
2. https://github.com/Treora/dom-highlight-range
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache BlueMarlin proposal

[Jean-Baptiste Onofre]

Hi Justin,

- Good point about the community. We know it’s a point we have to work 
generally speaking.
- +1 about the "inexperience with open source" section, I will add some content.
- Agree to start only with dev mailing list
- we are kindly asking for gitbox repo (not svn). It’s in the proposal draft: 
https://gitbox.apache.org/repos/asf/incubator/bluemarlin 

- the initial committer list is the actual team who created the project. We bet 
on the incubation phase to increase this list obviously. I will check with Xun 
if there is no miss in the initial committer list.
- I think we already have three good mentors but we wanted to add additional 
people to help building the community. If it’s a issue, we can reduce the list 
or invite new mentors on the podling.

Regards
JB


> Le 15 mars 2020 à 07:49, Justin Mclean  a écrit :
> 
> Hi,
> 
> They gave a presentation oat AupacheCon EU as part of the podling shark tank 
> and we’ve already had some discussion about this - obviously more has taken 
> place. It does sound like an interesting project.
> 
> Some suggestions/questions:
> -  I would like to see more in the proposal about the community and what 
> their expectation are there.
> - Under “inexperience with open source” it would be good to mention what 
> projects and if they have any committer or PMC members in other projects.
> - Under required resources it best to have a single dev list without a user 
> list to start off. The names of the list are not what are normally asked for 
> is there a reason for that?
> - Most projects seem to be using git these days, is there a reason svn is 
> asked for?
> - The initially committers seems small, are there any other people involved 
> in the project that might be considered as committers? [1] only show three 
> main committers. How do these match up with the four initial committers?
> - One of the proposed mentors is not an ASF member or IPMC member and so 
> would be unable to be a mentor and two may have a few too many incubating 
> project on their plate to be effective mentors. Of course only they would be 
> a good judge of that. One mentor is fairly new to mentoring.  Does the 
> project think it has the right mix of mentors that will be able to help the 
> project graduate?
> 
> Thanks,
> Justin
> 
> 1. https://github.com/Futurewei-io/blue-marlin/graphs/contributors
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Release Apache ECharts (incubating) 4.7.0 (release candidate 1)

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- incubating in name
- signatures and hashes are correct
- LICENSE and NOTICE are fine
- No binary files in release
- All source files have ASF header
- Can “compile"

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Tuweni 1.0.0-incubating release

[Justin Mclean]

Hi,

+1 (binding)

I checked only the source release:
- incubating in name
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE are good
- No unexpected binary files
- Hard to tell if any files are missing headers due to large number of Json 
files
- Didn’t compile from source

It a little unclear from the names if if gossip and relayer are binary or 
source artefacts, you might want to correct that.

Also you might want consider  removing the large amount of test resource form 
the source release, IMO users generally want to build the release not test it 
ands it on the rather large size with some test file being over 1Mb.

Thanks,
Justin



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache BlueMarlin proposal

[Justin Mclean]

Hi,

They gave a presentation oat AupacheCon EU as part of the podling shark tank 
and we’ve already had some discussion about this - obviously more has taken 
place. It does sound like an interesting project.

Some suggestions/questions:
-  I would like to see more in the proposal about the community and what their 
expectation are there.
- Under “inexperience with open source” it would be good to mention what 
projects and if they have any committer or PMC members in other projects.
- Under required resources it best to have a single dev list without a user 
list to start off. The names of the list are not what are normally asked for is 
there a reason for that?
- Most projects seem to be using git these days, is there a reason svn is asked 
for?
- The initially committers seems small, are there any other people involved in 
the project that might be considered as committers? [1] only show three main 
committers. How do these match up with the four initial committers?
- One of the proposed mentors is not an ASF member or IPMC member and so would 
be unable to be a mentor and two may have a few too many incubating project on 
their plate to be effective mentors. Of course only they would be a good judge 
of that. One mentor is fairly new to mentoring.  Does the project think it has 
the right mix of mentors that will be able to help the project graduate?

Thanks,
Justin

1. https://github.com/Futurewei-io/blue-marlin/graphs/contributors


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[DISCUSS] Apache BlueMarlin proposal

[Jean-Baptiste Onofre]

Hi,

With other guys, I worked on a new proposal for the Apache Incubator: Apache 
BlueMarlin.

The proposal draft is there:

https://cwiki.apache.org/confluence/display/INCUBATOR/Apache+BlueMarlin 


Even if the people behind BlueMarlin are a bit "new" to Apache, they are really 
enthusiasts and asked help to several Apache members.

From a project standpoint, it’s interesting as it’s new area that we don’t have 
yet in the Apache foundation. Building a framework for web 
marketing/advertising business is interesting IMHO and we could see several 
platforms based on BlueMarlin.

Thoughts ?

Regards
JB