Re: [DISCUSS] Mysos Incubation proposal
I am in favor of incubating Mysos, although I wonder if it might be better incubated as a subproject of Mesos rather than its own top-level project. I'm not yet familiar with all the intricacies of subprojects. While I acknowledge the phonetic/typographic similarity, some of us within the Apache Mesos community see it as a familiar pattern, following pesos https://github.com/wickman/pesos (Python bindings for Mesos) and jesos https://github.com/groupon/jesos (Java bindings for Mesos). But I can imagine getting especially confused switching between MESOS-123 and MYSOS-123. On Fri, May 8, 2015 at 3:06 PM, jan i j...@apache.org wrote: On Friday, May 8, 2015, Jiang Yan Xu y...@jxu.me wrote: Maybe in as many places as possible we could spell out the portmanteau as Mysos: MySQL on Mesos. +1 count me in as being confused, but this suggestion helps. rgds jan i Yan --- Jiang Yan Xu y...@jxu.me javascript:; | @xujyan https://twitter.com/xujyan On Thu, May 7, 2015 at 5:47 PM, Ted Dunning ted.dunn...@gmail.com javascript:; wrote: No. I mean Mysos / Mesos phonetic and typographic similarity. It took 5-10 lines of reading for me to understand the Mysos was not a typo. Until then, I was just confused. And I had heard of this effort before. It is just a data point. Not any kind of strong comment. On Fri, May 8, 2015 at 1:39 AM, Henry Saputra henry.sapu...@gmail.com javascript:; wrote: Do you mean about it being Apache Mesos framework ? In Mesos world, a framework is like an application build to run on top of Mesos. We should probably change the definition to be more clear from the outside of Mesos community. - Henry On Thu, May 7, 2015 at 4:01 PM, Ted Dunning ted.dunn...@gmail.com javascript:; wrote: On Thu, May 7, 2015 at 7:47 PM, Dave Lester d...@davelester.org javascript:; wrote: Mysos is an Apache Mesos framework That is a very confusing name (to me) at least. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; -- Sent from My iPad, sorry for any misspellings.
Re: [VOTE] Release Apache htrace-3.2.0-incubating
Hi, Good eyes on the LICENSE and NOTICE files. These are documentation issues not license errors, as long as it fixed next release/before graduation all good. I think the issue is that leveldb-devel isn't installed on your machine. Would this be something we could fix in a follow up release? It’s important that the software can be compiled from source without error. [1][2] I can confirm that once I installed leveldb I was able to compile the package. It may be acceptable to add that to the announce email. What do other incubator members think? Thanks, Justin 1. http://www.apache.org/dev/release.html#what-must-every-release-contain http://www.apache.org/dev/release.html#what-must-every-release-contain 2. http://incubator.apache.org/guides/releasemanagement.html#check-list http://incubator.apache.org/guides/releasemanagement.html#check-list (2.1)
Re: [VOTE] Release Apache htrace-3.2.0-incubating
Hey Justin, Thanks for taking the time to review the RC. Good eyes on the LICENSE and NOTICE files. Some notes there: - Backbone.* is bundled in marionette - The other dependencies that might not need to be listed probably don't since I think we simply download them: https://github.com/apache/incubator-htrace/blob/master/htrace-core/src/go/Godeps/Godeps.json . I think the issue is that leveldb-devel isn't installed on your machine. Looking at https://github.com/apache/incubator-htrace/blob/master/BUILDING.txt, it seems like we forgot to move the dependency list to htrace-htraced from htrace-core ( https://github.com/apache/incubator-htrace/blob/master/htrace-core/src/go/BUILDING.txt). Would this be something we could fix in a follow up release? -Abe On Sun, May 10, 2015 at 5:00 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, +0 (binding) due to compile issue. Happy to change to +1 if that's resolved/explained. The LICENSE and NOTICE issues can be fixed next release IMO. I checked: - hashes and signatures good - artefact name includes incubating - DISCLAIMER exits - Some minor LICENSE and NOTICE issues (see below) - No unexpected binaries in release - All source has Apache headers - Error compiling from source NOTICE has several minor issues: - Text is wrong as is states software developed by The Apache Software Foundation” when it should say software developed at The Apache Software Foundation”. Note “by” vs “at”. - NOTICE is missing copyright year - No need to include Apache licensed software in NOTICE (unless it has a NOTICE file) [1] - Probably no need to add public domain software in NOTICE, but it can go in LICENSE like other permissive licenses. [2] The LICENSE may have several items that don’t need to be in there, only bundled software needs to be in the license. [3] From a quick look I’m not sure that Levigo, Kingpin, Units, Gorilla mux, Backbone.Wreqr or Backbone.Babysitter are bundled. Looks like LICENSE is missing normalize.css (v2.1.0 | MIT License at git.io/normalize). Also good to place the RC in the correct location [4] and not on people.apache.org. I’m currently getting the compile failing - with this error: main: [exec] godep restore... [exec] fatal: Not a git repository (or any of the parent directories): .git [exec] github.com/jmhodges/levigo [exec] # github.com/jmhodges/levigo [exec] src/github.com/jmhodges/levigo/batch.go:4:11: fatal error: 'leveldb/c.h' file not found [exec] #include leveldb/c.h [exec] ^ [exec] 1 error generated. [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache HTrace . SUCCESS [ 1.577 s] [INFO] htrace-c .. SUCCESS [ 0.456 s] [INFO] htrace-core ... SUCCESS [ 12.161 s] [INFO] htrace-zipkin . SUCCESS [ 5.404 s] [INFO] htrace-hbase .. SUCCESS [ 30.739 s] [INFO] htrace-flume .. SUCCESS [ 19.688 s] [INFO] htrace-htraced FAILURE [ 2.290 s] [INFO] [INFO] BUILD FAILURE Any idea what may be causing the compile error? Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#alv2-dep 2. http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products 3. http://www.apache.org/dev/licensing-howto.html#guiding-principle 4. http://incubator.apache.org/guides/releasemanagement.html#glossary-incubator-dist - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Trafodion Incubation Proposal
On Sun, May 10, 2015 at 7:13 PM, Konstantin Boudnik c...@apache.org wrote: I think it'd be great to have SQL platform for Hadoop +1 I am mentoring 4 projects at the moment, but if you need a 1/2 time mentor - count me in ;) Cos We'll take you up on your kind offer if we can't get someone less loaded. Thanks Cos, St.Ack On Fri, May 08, 2015 at 02:59PM, Stack wrote: I would like to start up a discussion on Trafodion joining the ASF as an incubating project. Trafodion is a webscale SQL-on-Hadoop solution that enables transactional or operational workloads on Hadoop, . The proposal is available on the wiki here: https://wiki.apache.org/incubator/TrafodionProposal#preview The proposal text is also attached to the end of this email. Trafodion is a rich, storied SQL engine that has recently been ported to run on HBase and Hadoop. I think it would make for a fine addition to the Apache family of projects It would be good to hear what others think. Thank you in advance for giving the proposal a read. Yours, St.Ack Trafodion Apache Incubator Proposal Abstract Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Proposal Apache Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Key features of Apache Trafodion include: * Full-functioned ANSI SQL language support * JDBC/ODBC connectivity for Linux/Windows clients * Distributed ACID transaction protection across multiple statements, tables and rows * Performance improvements for OLTP workloads with compile-time and run-time optimizations * Support for large data sets using a parallel-aware query optimizer * ANSI SQL security and data integrity constraints including referential integrity Hewlett-Packard Company submits this proposal to donate its Apache License, Version 2.0 open source project known as Trafodion, its source code, documentation, and web site content to the Apache Software Foundation in order to build an open source community Background Trafodion is an open source project sponsored by HP, incubated at HP Labs and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting big data transactional or operational workloads. HP publically announced the open source project and uploaded the source code to GitHub in June 2014. The SQL compiler, optimizer and executor components of Trafodion have a rich heritage. Under development since 1993, they were released as commercial closed source software in various flavors such as HP NonStop SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is known for its high availability, scalability, and performance. Hundreds of companies and thousands of servers are running mission-critical applications today on NonStop SQL/MX. In addition, much of these components today are running internal to HP as the core of its Enterprise Data Warehouse (EDW), managing over a PB of data. Starting in 2013, the software was modified to run on HBase and a new distributed transaction manager was written to run as an HBase co-processor. Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion provides comprehensive ANSI SQL language support including full-functioned data definition (DDL), data manipulation (DML), transaction control (TCL) and database utility support. Trafodion provides comprehensive and standard SQL data manipulation support including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with language options including join variants, unions, where predicates, aggregations (group by and having), sort ordering, sampling, correlated and nested sub-queries, cursors, and many SQL functions. Utilities are provided for updating table statistics used by the optimizer for costing (i.e. selectivity/cardinality estimates) plan alternatives, for displaying the chosen SQL execution plan, plan shaping, backup and restoring the database, data loading and unloading, and a command line utility for interfacing with the database engine. Explicit control statements are provided to allow applications to define transaction boundaries and to abort transactions when warranted, including BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION. Trafodion supports ANSI’s grant/revoke semantics to define user and role privileges in terms of managing and accessing the database objects. Rationale The name “Trafodion” (the Welsh word for transactions, pronounced “Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation that Trafodion provides in closing a critical gap in the
Re: [VOTE] Release Apache htrace-3.2.0-incubating
On Sun, May 10, 2015 at 7:30 PM, Justin Mclean jus...@classsoftware.com wrote: What do other incubator members think? I think you are a good man for trying the candidate. Thanks Justin. The compile fail is pretty ugly. Your suggestion of a banner warning on the release email sounds like a good idea to me (otherwise, we sink the release candidate). Thanks, St.Ack
Re: [DISCUSS] Trafodion Incubation Proposal
I think this would be a great addition, and I am sure this will help fix the committer diversity. -Dan On Fri, May 8, 2015 at 2:59 PM, Stack st...@duboce.net wrote: I would like to start up a discussion on Trafodion joining the ASF as an incubating project. Trafodion is a webscale SQL-on-Hadoop solution that enables transactional or operational workloads on Hadoop, . The proposal is available on the wiki here: https://wiki.apache.org/incubator/TrafodionProposal#preview The proposal text is also attached to the end of this email. Trafodion is a rich, storied SQL engine that has recently been ported to run on HBase and Hadoop. I think it would make for a fine addition to the Apache family of projects It would be good to hear what others think. Thank you in advance for giving the proposal a read. Yours, St.Ack Trafodion Apache Incubator Proposal Abstract Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Proposal Apache Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Key features of Apache Trafodion include: * Full-functioned ANSI SQL language support * JDBC/ODBC connectivity for Linux/Windows clients * Distributed ACID transaction protection across multiple statements, tables and rows * Performance improvements for OLTP workloads with compile-time and run-time optimizations * Support for large data sets using a parallel-aware query optimizer * ANSI SQL security and data integrity constraints including referential integrity Hewlett-Packard Company submits this proposal to donate its Apache License, Version 2.0 open source project known as Trafodion, its source code, documentation, and web site content to the Apache Software Foundation in order to build an open source community Background Trafodion is an open source project sponsored by HP, incubated at HP Labs and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting big data transactional or operational workloads. HP publically announced the open source project and uploaded the source code to GitHub in June 2014. The SQL compiler, optimizer and executor components of Trafodion have a rich heritage. Under development since 1993, they were released as commercial closed source software in various flavors such as HP NonStop SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is known for its high availability, scalability, and performance. Hundreds of companies and thousands of servers are running mission-critical applications today on NonStop SQL/MX. In addition, much of these components today are running internal to HP as the core of its Enterprise Data Warehouse (EDW), managing over a PB of data. Starting in 2013, the software was modified to run on HBase and a new distributed transaction manager was written to run as an HBase co-processor. Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion provides comprehensive ANSI SQL language support including full-functioned data definition (DDL), data manipulation (DML), transaction control (TCL) and database utility support. Trafodion provides comprehensive and standard SQL data manipulation support including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with language options including join variants, unions, where predicates, aggregations (group by and having), sort ordering, sampling, correlated and nested sub-queries, cursors, and many SQL functions. Utilities are provided for updating table statistics used by the optimizer for costing (i.e. selectivity/cardinality estimates) plan alternatives, for displaying the chosen SQL execution plan, plan shaping, backup and restoring the database, data loading and unloading, and a command line utility for interfacing with the database engine. Explicit control statements are provided to allow applications to define transaction boundaries and to abort transactions when warranted, including BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION. Trafodion supports ANSI’s grant/revoke semantics to define user and role privileges in terms of managing and accessing the database objects. Rationale The name “Trafodion” (the Welsh word for transactions, pronounced “Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation that Trafodion provides in closing a critical gap in the Hadoop ecosystem. Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Current Status HP released the Trafodion code under the Apache License, Version 2, in June of
Re: JavaX
On Sat, May 09, 2015 at 02:28PM, Stefan Reich wrote: Hi incubators! :-) I'd like to find a home for the JavaX project (http://javax.tinybrain.de). JavaX is a super-extensible version of Java. It's probably the easiest way to extend any language existing right now. Translators for language extensions are collected in a central repository for everyone to use. JavaX's current download is 18k (very compact), yet it does all I need it to do thanks to the flexible translation architecture that downloads language extensions from the repository on the fly. (There is certainly stuff to add though, like support for Windows.) We also have a little user group in Hamburg ( http://meetup.com/JavaX-User-Group/). If Apache is interested, I'd have the following offer: As far as I am concerned, Apache can proceed in any way the like. You can subject the language to an organisational process, install stewards, publish the language and so on. The stewards don't even have to be or include me. :-) Do you want to come to the Apache and build a community of like-minded people to advance the project further? If so - the Incubator is the right place to start. If you simply want to donate the code: as Ted said Apache won't simply take over :) The one thing I require is that I retain the right to do the same thing - publish and talk about the language by myself, call my products JavaX and so on. That's totally permitted under the ASL2.0 terms. There're some restrictions on how the Apache project names could be used, but that's pretty much all. E.g. you can make a project Bar that include Apache Foo and call it Apache Foo. However, you can totally say Bar including (or powered by) Apache Foo. So there might be a split, but I wouldn't even find that bad. If there is no split and we all collaborate - that is also acceptable. I don't know if I want to be an official part of the ASF or so... that is why I propose that other way of you actually doing what you want. Of course I always like to advise, but as I said, you as a foundation could even grab the whole language and call it yours. I am a very open person. Are you working alone on the project? Do you have any other contributors to the code base? Perhaps it might be a good seed for the new community? Hope it helps a bit. Cos Tell me if and how you'd all like to proceed :-) All the best, Stefan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Trafodion Incubation Proposal
I think it'd be great to have SQL platform for Hadoop +1 I am mentoring 4 projects at the moment, but if you need a 1/2 time mentor - count me in ;) Cos On Fri, May 08, 2015 at 02:59PM, Stack wrote: I would like to start up a discussion on Trafodion joining the ASF as an incubating project. Trafodion is a webscale SQL-on-Hadoop solution that enables transactional or operational workloads on Hadoop, . The proposal is available on the wiki here: https://wiki.apache.org/incubator/TrafodionProposal#preview The proposal text is also attached to the end of this email. Trafodion is a rich, storied SQL engine that has recently been ported to run on HBase and Hadoop. I think it would make for a fine addition to the Apache family of projects It would be good to hear what others think. Thank you in advance for giving the proposal a read. Yours, St.Ack Trafodion Apache Incubator Proposal Abstract Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Proposal Apache Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Key features of Apache Trafodion include: * Full-functioned ANSI SQL language support * JDBC/ODBC connectivity for Linux/Windows clients * Distributed ACID transaction protection across multiple statements, tables and rows * Performance improvements for OLTP workloads with compile-time and run-time optimizations * Support for large data sets using a parallel-aware query optimizer * ANSI SQL security and data integrity constraints including referential integrity Hewlett-Packard Company submits this proposal to donate its Apache License, Version 2.0 open source project known as Trafodion, its source code, documentation, and web site content to the Apache Software Foundation in order to build an open source community Background Trafodion is an open source project sponsored by HP, incubated at HP Labs and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting big data transactional or operational workloads. HP publically announced the open source project and uploaded the source code to GitHub in June 2014. The SQL compiler, optimizer and executor components of Trafodion have a rich heritage. Under development since 1993, they were released as commercial closed source software in various flavors such as HP NonStop SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is known for its high availability, scalability, and performance. Hundreds of companies and thousands of servers are running mission-critical applications today on NonStop SQL/MX. In addition, much of these components today are running internal to HP as the core of its Enterprise Data Warehouse (EDW), managing over a PB of data. Starting in 2013, the software was modified to run on HBase and a new distributed transaction manager was written to run as an HBase co-processor. Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion provides comprehensive ANSI SQL language support including full-functioned data definition (DDL), data manipulation (DML), transaction control (TCL) and database utility support. Trafodion provides comprehensive and standard SQL data manipulation support including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with language options including join variants, unions, where predicates, aggregations (group by and having), sort ordering, sampling, correlated and nested sub-queries, cursors, and many SQL functions. Utilities are provided for updating table statistics used by the optimizer for costing (i.e. selectivity/cardinality estimates) plan alternatives, for displaying the chosen SQL execution plan, plan shaping, backup and restoring the database, data loading and unloading, and a command line utility for interfacing with the database engine. Explicit control statements are provided to allow applications to define transaction boundaries and to abort transactions when warranted, including BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION. Trafodion supports ANSI’s grant/revoke semantics to define user and role privileges in terms of managing and accessing the database objects. Rationale The name “Trafodion” (the Welsh word for transactions, pronounced “Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation that Trafodion provides in closing a critical gap in the Hadoop ecosystem. Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Current Status HP released the
Re: [VOTE] Release Apache htrace-3.2.0-incubating
Hi, +0 (binding) due to compile issue. Happy to change to +1 if that's resolved/explained. The LICENSE and NOTICE issues can be fixed next release IMO. I checked: - hashes and signatures good - artefact name includes incubating - DISCLAIMER exits - Some minor LICENSE and NOTICE issues (see below) - No unexpected binaries in release - All source has Apache headers - Error compiling from source NOTICE has several minor issues: - Text is wrong as is states software developed by The Apache Software Foundation” when it should say software developed at The Apache Software Foundation”. Note “by” vs “at”. - NOTICE is missing copyright year - No need to include Apache licensed software in NOTICE (unless it has a NOTICE file) [1] - Probably no need to add public domain software in NOTICE, but it can go in LICENSE like other permissive licenses. [2] The LICENSE may have several items that don’t need to be in there, only bundled software needs to be in the license. [3] From a quick look I’m not sure that Levigo, Kingpin, Units, Gorilla mux, Backbone.Wreqr or Backbone.Babysitter are bundled. Looks like LICENSE is missing normalize.css (v2.1.0 | MIT License at git.io/normalize). Also good to place the RC in the correct location [4] and not on people.apache.org. I’m currently getting the compile failing - with this error: main: [exec] godep restore... [exec] fatal: Not a git repository (or any of the parent directories): .git [exec] github.com/jmhodges/levigo [exec] # github.com/jmhodges/levigo [exec] src/github.com/jmhodges/levigo/batch.go:4:11: fatal error: 'leveldb/c.h' file not found [exec] #include leveldb/c.h [exec] ^ [exec] 1 error generated. [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache HTrace . SUCCESS [ 1.577 s] [INFO] htrace-c .. SUCCESS [ 0.456 s] [INFO] htrace-core ... SUCCESS [ 12.161 s] [INFO] htrace-zipkin . SUCCESS [ 5.404 s] [INFO] htrace-hbase .. SUCCESS [ 30.739 s] [INFO] htrace-flume .. SUCCESS [ 19.688 s] [INFO] htrace-htraced FAILURE [ 2.290 s] [INFO] [INFO] BUILD FAILURE Any idea what may be causing the compile error? Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#alv2-dep 2. http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products 3. http://www.apache.org/dev/licensing-howto.html#guiding-principle 4. http://incubator.apache.org/guides/releasemanagement.html#glossary-incubator-dist - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Apache TinkerPop 3.0.0.M8-incubating Release (Part Deux)
Was this vote ever resolved? On Mon, Apr 27, 2015 at 11:21 AM Marko Rodriguez okramma...@gmail.com wrote: Hello, Make sure to include a voting record, not just the summary votes. It helps to point at a single result e-mail to see everyone who voted, rather than having to dig through the thread. Understood. The URL to the bottom of the [VOTE] thread is here: https://www.mail-archive.com/general@incubator.apache.org/msg48404.html Congratulations on the successful release. Thanks -- and to the people who reviewed and voted. We appreciate you all helping us get our pattern down which should make future releases clock work. Take care, Marko. http://markorodriguez.com Take care, Marko. http://markorodriguez.com On Apr 25, 2015, at 2:09 PM, Henry Saputra henry.sapu...@gmail.com wrote: Signature file good Hashes file good LICENSE file good NOTICE file exists and GOOD No 3rd part executables in source package. +1 binding Good job - Henry On Fri, Apr 24, 2015 at 2:21 PM, Marko Rodriguez okramma...@gmail.com wrote: Hello everyone, We need one more +1 vote to release. A review would be much appreciated. Thank you, Marko. http://markorodriguez.com On Apr 23, 2015, at 6:31 PM, Matt Franklin m.ben.frank...@gmail.com wrote: +1 binding On Tue, Apr 21, 2015 at 10:03 PM Justin Mclean jus...@classsoftware.com wrote: Hi, (sending again as sent from wrong address first time) +1 binding For the source release I checked: - incubating in artifact name - signatures and hashes good - LICENSE and NOTICE ok - All source files have Apache headers - No unexpected binary files - Still can’t compile from source but it tells me I have wrong java version - most of the issues raised from the last release have been fixed Minor issues - please fix for next release. - No need to add normalise.css to NOTICE as it is MIT licensed (Permissive licenses only need to be added to LICENSE in most cases - the main exceptions being Apache licensed software with NOTICE files and files that have had their copyright removed). The copyright notice here should go into LICENSE. - I'm still not sure of the reason why some of the artefacts are named gremlin rather than tinkerpop Thanks, Justin - 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
Board Report Problems
All,
In the report_runbook for the month, we include the following text:
##
# editorial -- Assemble list of releases.
#
# The Board report must contain a list of releases by the
# Incubator project since the last report. This can be assembled
# manually from the history of our dist area.
#
# The date of each release is the date it appeared in our dist
# area. Since our report periods don't have hard boundaries,
# the only way to know which reports made the cut last month and
# which didn't is to check the last report.
##
# History of our dist area since just before the last report:
svn log -v -r {2015-04-01}:HEAD
https://dist.apache.org/repos/dist/release/incubator
I'm noticing that a lot of unapproved releases are ending up in here.
These are the ones I've identified, with no matching result vote (that I
can find)
Apache Sentry
Apache Streams (I can find rc3, but not 0.2)
Apache Tinkerpop (Probably my biggest concern, I see the vote thread, then
a cancel thread, yet their website lists the release, though it could be
the mail issues caused some mails to come in out of order on my side)
Apache REEF
If anyone can clarify, that would be super awesome.
John
[VOTE] Release Apache Commons RDF 0.1.0-incubating RC2
Hello, I am pleased to be calling this vote for the source release of Apache Commons RDF 0.1.0-incubating, composed by: * commons-rdf-api 0.1.0-incubating * commons-rdf-simple 0.1.0-incubating A candidate for the Commons RDF 0.1.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/commonsrdf/0.1.0-incubating/ The release candidate is based on the sources from commit 454ebc1ff457bcdb34f4671565bc984e6fbbcb77, tagged as 0.1.0-incubating, at: https://git-wip-us.apache.org/repos/asf/incubator-commonsrdf.git Release artifacts are signed with the keys available at: https://dist.apache.org/repos/dist/release/incubator/commonsrdf/KEYS A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecommons-1095 The changelog for this version is available from JIRA: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316620version=12332056 The current release has got 3 +1 votes (2 of them binding IPMC), with no 0 or -1 votes; the voting thread can be found at: http://s.apache.org/G2S This would represent the first incubating release of the podling, so we kindly ask you the Incubator PMC to carefully look to the release. Please vote on releasing this package as Apache Commons RDF 0.1.0-incubating. The vote is open for at least 72 hours and passes if a majority of at least three +1 IPMC votes are cast. [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernan...@redlink.co w: http://redlink.co
Re: Integrating JavaX
Stefan, Here is the email that I sent to general@ a few days ago. Didn't realize that you weren't subscribed. Note that I have bcc'ed the community development list and added general@incubator.apache.org We should continue the discussion there. You might like to subscribe so that replies made to the mailing list will reach you. I think it might help if we get a bit on the same page. Apache doesn't take over projects. Apache provides a framework for people involved in a project to create good releases and to build community. Check out resources on the web. I just found this, for instance, which is by an Apache member. It provides a reasonable outline of things. http://www.slideshare.net/hemapani/introduction-to-open-source-apache-and-apache-way On Sun, May 10, 2015 at 5:42 PM, Stefan Reich stefan.reich.maker.of@googlemail.com wrote: I wrote the mail... I thought you guys wanted to chime in? All the best, Stefan Am 08.05.2015 19:00 schrieb Konstantin Boudnik c...@apache.org: Stefan, As Thiago suggested, you can move this conversation to general@incubator.apache.org: there's a bunch of people who are helping new projects to get into ASF and up to speed on a daily basis. I, for one, will keep an eye on your email and will chime in as soon as it arrives ;) Good luck! Cos On Fri, May 08, 2015 at 06:41PM, Stefan Reich wrote: Nice! I'll make it a tech spike. Now we should move this discussion somewhere else I guess (sorry for posting to the list, Mike - I need attention :). Just where? Cheers Am 08.05.2015 17:34 schrieb Mike Kienenberger mkien...@gmail.com: javaX definitely looks interesting. I've always wished Java supported named parameter methods like Objective-C. drawCircleWithRadius:r atX:x y:y; instead of drawCircle(r, x, y); I suppose that would conflict with the conditional expression operator (b ? t : f) but maybe two colons drawCircleWithRadius::r atX::x y::y; Of course, without the smalltalk-esque grouping brackets, maybe it'd be too hard to read and parse it in java. Guess the idea would need more work. [renderer drawCircleWithRadius:r atX:[radiusSource xBasedOnInputA:a b:b] y:y]; versus renderer.drawCircleWithRadiusAtXandY(r, radiusSource.xBasedOnInputAandB(a, b), y); doesn't really work as renderer.drawCircleWithRadius::r atX::radiusSource.xBasedOnInputA::a b::b y::y; Maybe with extra parens... renderer.(drawCircleWithRadius::r atX::radiusSource.(xBasedOnInputA::a b::b) y::y); but at this point, it stops having the same readability Guess we really need objective C method call syntax for java :) On Fri, May 8, 2015 at 9:58 AM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Fri, 08 May 2015 09:18:10 -0300, Stefan Reich stefan.reich.maker.of@googlemail.com wrote: Hi! Hi! I'd like to find a home (or home-s) for the JavaX project ( http://javax.tinybrain.de). Taking a look . . . :) JavaX is a super-extensible version of Java. It's probably the easiest way to extend any language existing right now. Is there a way to collaborate with Apache? I think I can promise you that this is the way of the future :-) I believe the incubator is the place to start: http://incubator.apache.org/ The Incubator project is the entry path into The Apache Software Foundation (ASF) for projects and codebases wishing to become part of the Foundation's efforts. All code donations from external organisations and existing external projects wishing to join Apache enter through the Incubator. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br
Re: [RESULT] [VOTE] Apache TinkerPop 3.0.0.M8-incubating Release (Part Deux)
On Sun, May 10, 2015 at 6:05 AM, John D. Ament john.d.am...@gmail.com wrote:
svn log -v -r {2015-04-01}:HEAD
https://dist.apache.org/repos/dist/release/incubator
I'm noticing that a lot of unapproved releases are ending up in here.
These are the ones I've identified, with no matching result vote (that I
can find)
Apache Sentry
This one looks like a problem. A vote was taken for Sentry 1.5.0 on the
podling dev list, but there has been no vote on general@incubator.
http://mail-archives.apache.org/mod_mbox/incubator-sentry-dev/201504.mbox/%3CCAE=hR03kUTGF3s5QCpuUj=_eyry_gsR=w6kd-pvd_-cdcru...@mail.gmail.com%3E
It would be perfectly understandable for an individual release manager to
misunderstand the incubating release process, but it's troubling that not a
single podling community member spoke up. What's going on?
Apache Streams (I can find rc3, but not 0.2)
I find 0.2 here:
https://dist.apache.org/repos/dist/release/incubator/streams/releases/0.2-incubating/streams-project/
The vote for Streams 0.2 rc3 passed.
http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3CCAJ7ACC_FrCOy-qdn1+4J1k8Kn6=rbsuvnjvwgzugtn4k8_j...@mail.gmail.com%3E
Apache Tinkerpop (Probably my biggest concern, I see the vote thread, then
a cancel thread, yet their website lists the release, though it could be
the mail issues caused some mails to come in out of order on my side)
It would have been less confusing if Tinkerpop had used RC numbers instead of
Part Deux (French for part two) to indicate that a new vote was being
called on a new release candidate.
Nevertheless, the vote passed:
http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3cece3d22a-df79-4cb0-8f87-38717ba5a...@gmail.com%3E
Apache REEF
It looks like multiple release candidates for REEF 0.11.0-incubating have been
uploaded to the `releases` dir and then removed. The podling is currently
voting on RC6, which has been uploaded to the `dev` dir instead -- so it looks
like they've caught on.
...
In conclusion, I think that Sentry merits further investigation, but that
Streams, Tinkerpop and REEF are OK.
Marvin Humphrey
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
