Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC2

[Niclas Hedhman]

+1 binding

On Thu, Apr 20, 2017 at 4:10 PM, sospartan  wrote:

> Hi all,
> I'll calling a vote for Weex-incubating 0.12.0-RC2 release.
>
> The PPMC vote for this release has passed:
> https://lists.apache.org/thread.html/d544a60a4038f9d053f7ea1eca0d16
> 2b9aef392551a02a0401041e8f@%3Cdev.weex.apache.org%3E
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> ;a=shortlog;h=refs/tags/0.12.0-rc1
>
> The commit hash:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
> 9ac0c82443e65b1c9d8a2714fea6b9a5b8af9907
>
> The source tarball can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.
> 0-incubating/RC1/
>
> The fingerprint of key to sign release artifacts:
> 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
>
> Release note about this version:
> https://issues.apache.org/jira/browse/WEEX-26
>
> This vote will remain open for at least 72 hours.
> Please vote on releasing this RC.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> --
> Best Regards!
> --
>
> sospartan
> https://weex-project.io
>



-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

Re: Edit access to add proposal

[Marvin Humphrey]

On Thu, Apr 20, 2017 at 5:06 PM, Bryan Call  wrote:
> I would like to request edit access, so I can add a proposal.
> My username is BryanCall.

Done.

Marvin Humphrey

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

Edit access to add proposal

[Bryan Call]

I would like to request edit access, so I can add a proposal.  My username is 
BryanCall.

Thank you,

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

Re: [VOTE]: Apache HAWQ 2.2.0.0-incubating Release

[Roman Shaposhnik]

On Thu, Apr 20, 2017 at 7:05 AM, Ruilong Huo  wrote:
> Thanks Roman for the verification! We will fix the issue and keep updated
> in the community.

Thanks for your understanding! Lets take it back to dev@hawq where I can
help you guys with the required changes.

Thanks,
Roman.

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

Re: [VOTE] Accept Amaterasu into the Apache Incubator

[Felix Cheung]

+1 (non binding)

On Wed, Apr 19, 2017 at 4:59 PM Olivier Lamy  wrote:

> +1 (binding)
>
> On 17 April 2017 at 04:20, Jean-Baptiste Onofré  wrote:
>
> > Hi all,
> >
> > following the discussion thread, I think we can start the vote on
> > accepting Amaterasu into the Apache Incubator.
> >
> > The ASF voting rules are described:
> >
> > http://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for
> > which only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Amaterasu into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Amaterasu into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> >https://wiki.apache.org/incubator/AmaterasuProposal
> >
> > Note that we are looking for one more mentor on the proposal.
> > One concern has been raised about the "Amaterasu" name. We want to move
> > forward with Amaterasu name but open to change if needed.
> >
> > Thanks
> > Regards
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> > = Apache Amaterasu =
> >
> > == Abstract ==
> >
> > Apache Amaterasu is a framework providing continuous deployment for Big
> > Data pipelines.
> >
> > It provides the following capabilities:
> >
> >  * '''Continuous integration''' tools to '''package pipelines and run
> > tests'''.
> >  * A repository to store those packaged applications: the '''applications
> > repository'''.
> >  * A repository to store the pipelines, and engine configuration (for
> > instance, location of the Spark master, etc.): per environment - the
> > '''configuration repository'''.
> >  * A '''dashboard''' to monitor the pipelines.
> >  * A '''DSL and integration hooks''' allowing third parties to easily
> > integrate.
> >
> > == Proposal ==
> >
> > Amaterasu is a simple and powerful framework to build and dispense
> > pipelines. It aims to help data engineers and data scientists to compose,
> > configure, test, package, deploy and execute data pipelines written using
> > multiple tools, languages and frameworks. Amaterasu provides a standard
> > repo structure to package big data pipelines, a YAML based Domain
> Specific
> > Languages (DSL) for data engineers, data scientists and operations
> > engineers to manage complex pipelines throughout their entire lifecycle
> > (Dev, UAT, Prod, etc.).
> >
> > == Background ==
> >
> > Amaterasu is a relatively new project that was created to deal with some
> > of the issues that as Consultants, we have seen recurring at different
> > client sites. Mainly the need to continuously deploy complex pipelines
> > built in multiple tools and languages.
> > Amaterasu started as a pet project and is currently being evaluated by a
> > couple of organizations, supported by the contributors, on a personal
> time
> > and voluntary bases.
> >
> > == Rational ==
> >
> > As software engineers working on big data projects we have straggled for
> a
> > long time to apply the same CI/CD practices that have become the standard
> > in the software industry for the last few years. While some of them are
> > possible, for example Apache Spark is easy to unit test. However large
> > scale pipelines are more complex and often use data, which might be
> > un-structured as integration point, which requires heavy integration
> tests.
> >
> > To automate such tests and complex deployments, we have found the need to
> > often handcraft scripts and use a mixture tools, so we have decided to
> > finally build a tool we can apply in a general way and not on a project
> by
> > project basis.
> >
> > Another issue Amaterasu is trying to tackle is the Integrating between
> the
> > work of software engineers, data scientists, and sometimes operations
> > engineers. The approach Amaterasu takes to integrate between those three
> > schools of thought it to provide a simple YAML based DSL that provides a
> > simple way to integrate different pipeline written in the native tools
> for
> > each task (R, Spark in different languages, etc.).
> >
> > == Initial Goals ==
> >
> > Our initial goals are to bring Amaterasu into the ASF, transition
> internal
> > engineering processes into the open, and foster a collaborative
> development
> > model according to the "Apache Way".
> >
> > In addition, we intend to continue the development of Amaterasu, add new
> > features as well as  integrate better with other frameworks, including:
> >
> >  * Apache Arrow
> >  * Apache Hive
> >  * Apache Drill
> >  * Apache Beam
> >  * Apache YARN
> >  * Farther and more complete integration with Apache Spark
> >
> > Other frameworks will be evaluated after those initial goals are reached.
> >
> > == Current Status ==
> >
> > Amaterasu is preview state but provide a large set of features. 

Re: [VOTE]: Apache HAWQ 2.2.0.0-incubating Release

[Ruilong Huo]

Thanks Roman for the verification! We will fix the issue and keep updated
in the community.

Best regards,
Ruilong Huo

On Thu, Apr 20, 2017 at 2:02 PM, Roman Shaposhnik 
wrote:

> On Thu, Apr 13, 2017 at 6:30 AM, Ruilong Huo  wrote:
> > Hi All,
> >
> > The PPMC vote for the Apache HAWQ 2.2.0.0-incubating release has passed.
> We
> > kindly request that the IPMC now vote on the release.
> >
> > The PPMC vote thread is located here:
> > https://lists.apache.org/thread.html/a7c780cf5655679fa5c0cbe5a8d247
> 77cd0439601266260859f935ef@%3Cdev.hawq.apache.org%3E
> >
> > The artifacts can be downloaded here:
> > https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.
> 0-incubating.RC2/
> >
> > The artifacts have been signed with Key: 1B8B6872.
> >
> > All JIRAs completed for this release are tagged with 'FixVersion =
> > 2.2.0.0-incubating'. You can view them here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318826=12339641
> >
> > Please vote accordingly:
> > [ ] +1, accept as the official Apache HAWQ 2.2.0.0-incubating release
> > [ ] -1, do not accept as the official Apache HAWQ 2.2.0.0-incubating
> > release because...
> > The vote will run for at least 72 hours.
>
> I do apologize for a delay -- I should've provided this feedback last
> feedback
> last week, but it seems I'll be voting:
>
> -1 (binding)
>
> on the binary portion of this releases. Here's why:
> 1. The deal breaker issue is a total lack of clear IP attribution in
>  binary artifacts. There's no proper LICENSE, NOTICE and
>  DISCLAIMER file in neither the x86 binary package of HAWQ
>  nor in the JAVA packages of companion components. This
>  need to be fixed as per:
>  http://www.apache.org/dev/licensing-howto.html#binary
>  http://incubator.apache.org/guides/release-java.html#notes
>  Note that you HAVE to account to all the dependencies you're
>  bundling in a binary release which means your LICENSE and
>  NOTICE files will likely get bigger. For Java side of HAWQ
>  Apache Geode offers a good place to look for how to deal with
>  those files in a binary distribution.
>
>  2. This is one is less of a deal deal breaker for the first release,
> but
>  will be so for subsequent ones: you really shouldn't be shipping
>  apache-tomcat package. For one, you already have a dependency
>  on bigtop-tomcat in hawq-ranger-plugin which means shipping
>  apache-tomcat is wasteful, could conflicting with distribution RPM
>  names and frankly looks a bit sloppy coming from the same project.
>
>  3. This is even less of a dealbreaker than #2, but it may help you
>  simplify solving for #1: I don't think you need to ship all those
>  extra dependencies in hawq-ranger-plugin -- a much better option
>  is getting them from a classpath just like other Java packages of
>  HAWQ do.
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Thank you all. Can any IPMC member help review and vote this?

Sijie

On Apr 19, 2017 4:47 AM, "Jia Zhai"  wrote:

> +1(non-binding)
> - verified packages (md5, asc and sha1 all look good)
> - the source package build and test all run successfully.
> - NOTICE, DISCLAIMER, License headers look good.
>
> On Tue, Apr 18, 2017 at 8:36 PM, John D. Ament 
> wrote:
>
> > +1 to release
> >
> > - NOTICE file looks fine
> > - Source headers look correct
> > - DISCLAIMER present.
> >
> > On Tue, Apr 18, 2017 at 2:55 AM Sijie Guo  wrote:
> >
> > > Hi all,
> > >
> > > Please review and vote on the release candidate #4 for the Apache
> > > DistributedLog version 0.4.0-incubating, as follows:
> > >
> > > [ ] +1, Approve 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 to be deployed to
> > dist.apache.org
> > >  [2],
> > > * all artifacts to be deployed to the Maven Central Repository
> > [3][4],
> > > * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> > > "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> > > * website pull request listing the release [7] and publishing the
> API
> > > reference manual.
> > >
> > > The Apache DistributedLog community has unanimously approved this
> release
> > > [8].
> > >
> > > As customary, the vote will be open for at least 72 hours. It is
> adopted
> > > by a
> > > majority approval with at least three PMC affirmative votes. If
> approved,
> > > we
> > > will proceed with the release.
> > >
> > > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> > > ersion=12337980==12320620
> > > [2] https://dist.apache.org/repos/dist/dev/incubator/
> > distributedlog/0.4.0-
> > > incubating-RC4/
> > >  distributedlog/0.4.0-
> > incubating-RC4/>
> > > [3] https://repository.apache.org/content/repositories/
> > > orgapachedistributedlog-1007/
> > > [4] https://repository.apache.org/content/repositories/
> > > orgapachedistributedlog-1008/
> > > [5] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.11
> > > [6] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.10
> > > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > > [8]
> > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-
> > distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_
> > iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E
> > >
> >
>

Re: Coming to ApacheCON? Showcase your project at a Podling Shark Tank!

[Will Stevens]

OK thanks. The project I was thinking of is not a good fit. It is an
internal project related to Apache Cloudstack, but is unlikely that we push
to make it an apache project.

Thanks. :)

On Apr 20, 2017 2:44 AM, "Roman Shaposhnik"  wrote:

> On Wed, Apr 19, 2017 at 8:30 AM, Will Stevens 
> wrote:
> > I am assuming this is only for Apache projects that are in the incubator
> > phase?
> >
> > You don't want pitches for non-apache projects right?
>
> I can totally see a project that is seeking to joing the incubator
> pitching.
>
> What do you have in mind?
>
> Thanks,
> Roman.
>

[VOTE]: Apache Weex-incubating Release 0.12.0-RC2

[sospartan]

Hi all,
I'll calling a vote for Weex-incubating 0.12.0-RC2 release.

The PPMC vote for this release has passed:
https://lists.apache.org/thread.html/d544a60a4038f9d053f7ea1eca0d162b9aef392551a02a0401041e8f@%3Cdev.weex.apache.org%3E

The tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
;a=shortlog;h=refs/tags/0.12.0-rc1

The commit hash:
https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
9ac0c82443e65b1c9d8a2714fea6b9a5b8af9907

The source tarball can be found at:
https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC1/

The fingerprint of key to sign release artifacts:
97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS

Release note about this version:
https://issues.apache.org/jira/browse/WEEX-26

This vote will remain open for at least 72 hours.
Please vote on releasing this RC.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-- 
Best Regards!
--

sospartan
https://weex-project.io

Re: Coming to ApacheCON? Showcase your project at a Podling Shark Tank!

[Roman Shaposhnik]

On Wed, Apr 19, 2017 at 8:30 AM, Will Stevens  wrote:
> I am assuming this is only for Apache projects that are in the incubator
> phase?
>
> You don't want pitches for non-apache projects right?

I can totally see a project that is seeking to joing the incubator pitching.

What do you have in mind?

Thanks,
Roman.

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

Re: Coming to ApacheCON? Showcase your project at a Podling Shark Tank!

[Roman Shaposhnik]

On Tue, Apr 18, 2017 at 10:53 PM, Jean-Baptiste Onofré  
wrote:
> Hi Roman,
>
> do you think it would make sense to introduce nearly graduated podling,
> explaining the project and the journey in the incubator ? I'm thinking about
> Apache CarbonData for example.
>
> Thoughts ?

If we have slots available -- I'd say absolutely! Can I keep your offer in mind
and see how many podling will we have?

Thanks,
Roman.

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

Re: [VOTE]: Apache HAWQ 2.2.0.0-incubating Release

[Roman Shaposhnik]

On Thu, Apr 13, 2017 at 6:30 AM, Ruilong Huo  wrote:
> Hi All,
>
> The PPMC vote for the Apache HAWQ 2.2.0.0-incubating release has passed. We
> kindly request that the IPMC now vote on the release.
>
> The PPMC vote thread is located here:
> https://lists.apache.org/thread.html/a7c780cf5655679fa5c0cbe5a8d24777cd0439601266260859f935ef@%3Cdev.hawq.apache.org%3E
>
> The artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC2/
>
> The artifacts have been signed with Key: 1B8B6872.
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 2.2.0.0-incubating'. You can view them here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318826=12339641
>
> Please vote accordingly:
> [ ] +1, accept as the official Apache HAWQ 2.2.0.0-incubating release
> [ ] -1, do not accept as the official Apache HAWQ 2.2.0.0-incubating
> release because...
> The vote will run for at least 72 hours.

I do apologize for a delay -- I should've provided this feedback last feedback
last week, but it seems I'll be voting:

-1 (binding)

on the binary portion of this releases. Here's why:
1. The deal breaker issue is a total lack of clear IP attribution in
 binary artifacts. There's no proper LICENSE, NOTICE and
 DISCLAIMER file in neither the x86 binary package of HAWQ
 nor in the JAVA packages of companion components. This
 need to be fixed as per:
 http://www.apache.org/dev/licensing-howto.html#binary
 http://incubator.apache.org/guides/release-java.html#notes
 Note that you HAVE to account to all the dependencies you're
 bundling in a binary release which means your LICENSE and
 NOTICE files will likely get bigger. For Java side of HAWQ
 Apache Geode offers a good place to look for how to deal with
 those files in a binary distribution.

 2. This is one is less of a deal deal breaker for the first release, but
 will be so for subsequent ones: you really shouldn't be shipping
 apache-tomcat package. For one, you already have a dependency
 on bigtop-tomcat in hawq-ranger-plugin which means shipping
 apache-tomcat is wasteful, could conflicting with distribution RPM
 names and frankly looks a bit sloppy coming from the same project.

 3. This is even less of a dealbreaker than #2, but it may help you
 simplify solving for #1: I don't think you need to ship all those
 extra dependencies in hawq-ranger-plugin -- a much better option
 is getting them from a classpath just like other Java packages of
 HAWQ do.

Thanks,
Roman.

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