Re: September report
Busy night last night. Hoping to do it this morning. Regards, Alan On Sep 7, 2014, at 10:33 PM, Marvin Humphrey mar...@rectangular.com wrote: On Sun, Sep 7, 2014 at 9:57 PM, Roman Shaposhnik r...@apache.org wrote: Also, if there's anybody planning on creating a summary -- please let me know. Otherwise I'll do by the end of the day tomorrow. If this month's Report Manager needs support, I'm happy to pitch in. If we have to fall back to the PMC Chair handling the report, I'm also happy to pitch in. I'll check in tomorrow to see where things are at. Marvin Humphrey - 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: September report
Filled in a fair bit. I can’t get back to fill in the rest of the bits until later this afternoon. Regards, Alan On Sep 8, 2014, at 5:45 AM, Alan D. Cabrera l...@toolazydogs.com wrote: Busy night last night. Hoping to do it this morning. Regards, Alan On Sep 7, 2014, at 10:33 PM, Marvin Humphrey mar...@rectangular.com wrote: On Sun, Sep 7, 2014 at 9:57 PM, Roman Shaposhnik r...@apache.org wrote: Also, if there's anybody planning on creating a summary -- please let me know. Otherwise I'll do by the end of the day tomorrow. If this month's Report Manager needs support, I'm happy to pitch in. If we have to fall back to the PMC Chair handling the report, I'm also happy to pitch in. I'll check in tomorrow to see where things are at. Marvin Humphrey - 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] Release Apache Usergrid 1.0 (incubating)
Hi Dave, On Sun, Sep 7, 2014 at 12:39 PM, general-digest-h...@incubator.apache.org wrote: Here are the release files for release candidate 6: https://dist.apache.org/repos/dist/dev/incubator/usergrid/usergrid-1/v1.0.0/ Release candidate looking good. Tests and installs well for componments as per my previous comments over on usergrid lists. MD5 checksums for release files: apache-usergrid-incubating-1.0.0-rc6-source.tar.gz: 23 2F 12 D3 26 85 34 92 7C 7E A1 ED CF 52 75 71 apache-usergrid-incubating-1.0.0-rc6-source.zip: EF 1E 25 8C 01 F3 E4 6B A6 60 B9 72 1C 60 17 E7 Signatures good. Upon release the files will be renamed without rc6 in the filenames, but they will be the exact same and the above checksums will match. Sounds good to me. We then push them to https://dist.apache.org/repos/dist/release/incubator/usergrid/v1.0 Please note the v1.0 as oppose to 1.0.0. This will again prevent any confusion. The git tag for this release is 1.0.0 Which looks great. +1 binding Thanks for your persistence as release manager. Hopefully the process can be repeated and we can gather momentum now. Huge thank you to yourself Dave. Best Lewis
Re: [VOTE] Apache Drill 0.5.0-incubating release
On 7 September 2014 20:31, Jacques Nadeau jacq...@apache.org wrote: As I understand the release guidelines, one is not allowed to put something on dist.apache.org until after a release vote by the Incubator PMC approves that release: Only formally-approved releases may be distributed from the main directories [1] For this candidate, as with our last two releases, we followed this piece of information: It is traditional that release managers use their Apache home space to make available release candidates. [1] Historic tradition; that was before svnpubsub. Note that the DEV tree at https://dist.apache.org/repos/dist/dev/xyz is NOT published to www.apache.org/dist The svnpubsub process takes releases from the RELEASE tree at https://dist.apache.org/repos/dist/release/xyz Since they have the same parent, one can use svn move (or svnmucc) to transfer the files from dev to release area. This provides traceability (assuming the the release vote includes the SVN revision number) To date, we only push to dist.apache.org once we have received approval here. Can you point me to the guidelines that lead you to believe that this must be staged on dist.apache.org? Thanks, Jacques [1] http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote On Sun, Sep 7, 2014 at 11:48 AM, John D. Ament john.d.am...@gmail.com wrote: Sorry, I have to vote -1 The release is not staged in the proper place (e.g. https://dist.apache.org/repos/dist/dev/incubator/ ) If this gets moved, I can vote +1 On Sun, Sep 7, 2014 at 11:29 AM, Jacques Nadeau jacq...@apache.org wrote: Hi John, Thanks for the feedback. I'd like to respond to each of your concerns: Your NOTICE file is missing MIT license. The notice file states: Please see LICENSE for additional copyright and licensing information. The LICENSE file contains the MIT license. Your source file includes binaries in the sample-data directory. These are small sample data files that are used to do various unit tests. They have been approved on both of our previous releases because of their small size (24k combined) and the fact that they are not source code. These are raw data files that happen to be binary in nature but are for all purposes the same as example json files we include for testing purposes. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) The name of the release candidate directory is due to the nature of the Apache voting process. Each time we have a release candidate in the community, we hold a vote. We always maintain past release candidates so that we can refer back to them. All artifacts in the release candidate hold the release/public names and will ultimately be hosted on the Apache distribution servers at the appropriately named release directory. For historical perspective on this, see the following that has been our strategy thus far: our m1 release: http://people.apache.org/~jacques/apache-drill-1.0.0-m1 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc2 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc3 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4 (approved) -- and distributed as https://archive.apache.org/dist/incubator/drill/drill-1.0.0-m1-incubating/ our 0.4.0 release: http://people.apache.org/~jacques/apache-drill-0.4.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.4.0.rc1 (approved) -- distributed as https://archive.apache.org/dist/incubator/drill/drill-0.4.0-incubating/ our 0.5.0 release: http://people.apache.org/~jacques/apache-drill-0.5.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc1 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc2 (pending) As you can see, the rc numbers are only used during the voting process. Once we get approval from the incubator, we drop the rc so that external consumers aren't confused by failed released candidates. Hopefully this satisfies your concerns and you can vote +1 for our release. thanks again for your feedback, Jacques On Sun, Sep 7, 2014 at 5:09 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, Your NOTICE file is missing MIT license. Your source file includes binaries in the sample-data directory. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) John On Sat, Sep 6, 2014 at 11:36 PM, Jacques Nadeau jacq...@apache.org wrote: It is my pleasure to present the Apache Drill 0.5.0-incubating release to the general incubator list for a vote. This set of artifacts have passed our drill-dev vote and incorporate a number of improvements with over 100 JIRAs closed in the last month. As part of this release, we looked to address the feedback in our previous
Re: [VOTE] Apache Drill 0.5.0-incubating release
Is the new process documented somewhere? On Mon, Sep 8, 2014 at 3:17 PM, sebb seb...@gmail.com wrote: On 7 September 2014 20:31, Jacques Nadeau jacq...@apache.org wrote: As I understand the release guidelines, one is not allowed to put something on dist.apache.org until after a release vote by the Incubator PMC approves that release: Only formally-approved releases may be distributed from the main directories [1] For this candidate, as with our last two releases, we followed this piece of information: It is traditional that release managers use their Apache home space to make available release candidates. [1] Historic tradition; that was before svnpubsub. Note that the DEV tree at https://dist.apache.org/repos/dist/dev/xyz is NOT published to www.apache.org/dist The svnpubsub process takes releases from the RELEASE tree at https://dist.apache.org/repos/dist/release/xyz Since they have the same parent, one can use svn move (or svnmucc) to transfer the files from dev to release area. This provides traceability (assuming the the release vote includes the SVN revision number) To date, we only push to dist.apache.org once we have received approval here. Can you point me to the guidelines that lead you to believe that this must be staged on dist.apache.org? Thanks, Jacques [1] http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote On Sun, Sep 7, 2014 at 11:48 AM, John D. Ament john.d.am...@gmail.com wrote: Sorry, I have to vote -1 The release is not staged in the proper place (e.g. https://dist.apache.org/repos/dist/dev/incubator/ ) If this gets moved, I can vote +1 On Sun, Sep 7, 2014 at 11:29 AM, Jacques Nadeau jacq...@apache.org wrote: Hi John, Thanks for the feedback. I'd like to respond to each of your concerns: Your NOTICE file is missing MIT license. The notice file states: Please see LICENSE for additional copyright and licensing information. The LICENSE file contains the MIT license. Your source file includes binaries in the sample-data directory. These are small sample data files that are used to do various unit tests. They have been approved on both of our previous releases because of their small size (24k combined) and the fact that they are not source code. These are raw data files that happen to be binary in nature but are for all purposes the same as example json files we include for testing purposes. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) The name of the release candidate directory is due to the nature of the Apache voting process. Each time we have a release candidate in the community, we hold a vote. We always maintain past release candidates so that we can refer back to them. All artifacts in the release candidate hold the release/public names and will ultimately be hosted on the Apache distribution servers at the appropriately named release directory. For historical perspective on this, see the following that has been our strategy thus far: our m1 release: http://people.apache.org/~jacques/apache-drill-1.0.0-m1 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc2 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc3 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4 (approved) -- and distributed as https://archive.apache.org/dist/incubator/drill/drill-1.0.0-m1-incubating/ our 0.4.0 release: http://people.apache.org/~jacques/apache-drill-0.4.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.4.0.rc1 (approved) -- distributed as https://archive.apache.org/dist/incubator/drill/drill-0.4.0-incubating/ our 0.5.0 release: http://people.apache.org/~jacques/apache-drill-0.5.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc1 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc2 (pending) As you can see, the rc numbers are only used during the voting process. Once we get approval from the incubator, we drop the rc so that external consumers aren't confused by failed released candidates. Hopefully this satisfies your concerns and you can vote +1 for our release. thanks again for your feedback, Jacques On Sun, Sep 7, 2014 at 5:09 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, Your NOTICE file is missing MIT license. Your source file includes binaries in the sample-data directory. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) John On Sat, Sep 6, 2014 at 11:36 PM, Jacques Nadeau jacq...@apache.org wrote: It is my pleasure to present the Apache Drill 0.5.0-incubating release to the general incubator
Re: [VOTE] Apache Drill 0.5.0-incubating release
Ted, Do you mean more than here: [1]: http://www.apache.org/dev/publishing-maven-artifacts.html [2]: http://www.apache.org/dev/release.html#host-rc On Mon, Sep 8, 2014 at 7:12 PM, Ted Dunning ted.dunn...@gmail.com wrote: Is the new process documented somewhere? On Mon, Sep 8, 2014 at 3:17 PM, sebb seb...@gmail.com wrote: On 7 September 2014 20:31, Jacques Nadeau jacq...@apache.org wrote: As I understand the release guidelines, one is not allowed to put something on dist.apache.org until after a release vote by the Incubator PMC approves that release: Only formally-approved releases may be distributed from the main directories [1] For this candidate, as with our last two releases, we followed this piece of information: It is traditional that release managers use their Apache home space to make available release candidates. [1] Historic tradition; that was before svnpubsub. Note that the DEV tree at https://dist.apache.org/repos/dist/dev/xyz is NOT published to www.apache.org/dist The svnpubsub process takes releases from the RELEASE tree at https://dist.apache.org/repos/dist/release/xyz Since they have the same parent, one can use svn move (or svnmucc) to transfer the files from dev to release area. This provides traceability (assuming the the release vote includes the SVN revision number) To date, we only push to dist.apache.org once we have received approval here. Can you point me to the guidelines that lead you to believe that this must be staged on dist.apache.org? Thanks, Jacques [1] http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote On Sun, Sep 7, 2014 at 11:48 AM, John D. Ament john.d.am...@gmail.com wrote: Sorry, I have to vote -1 The release is not staged in the proper place (e.g. https://dist.apache.org/repos/dist/dev/incubator/ ) If this gets moved, I can vote +1 On Sun, Sep 7, 2014 at 11:29 AM, Jacques Nadeau jacq...@apache.org wrote: Hi John, Thanks for the feedback. I'd like to respond to each of your concerns: Your NOTICE file is missing MIT license. The notice file states: Please see LICENSE for additional copyright and licensing information. The LICENSE file contains the MIT license. Your source file includes binaries in the sample-data directory. These are small sample data files that are used to do various unit tests. They have been approved on both of our previous releases because of their small size (24k combined) and the fact that they are not source code. These are raw data files that happen to be binary in nature but are for all purposes the same as example json files we include for testing purposes. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) The name of the release candidate directory is due to the nature of the Apache voting process. Each time we have a release candidate in the community, we hold a vote. We always maintain past release candidates so that we can refer back to them. All artifacts in the release candidate hold the release/public names and will ultimately be hosted on the Apache distribution servers at the appropriately named release directory. For historical perspective on this, see the following that has been our strategy thus far: our m1 release: http://people.apache.org/~jacques/apache-drill-1.0.0-m1 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc2 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc3 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4 (approved) -- and distributed as https://archive.apache.org/dist/incubator/drill/drill-1.0.0-m1-incubating/ our 0.4.0 release: http://people.apache.org/~jacques/apache-drill-0.4.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.4.0.rc1 (approved) -- distributed as https://archive.apache.org/dist/incubator/drill/drill-0.4.0-incubating/ our 0.5.0 release: http://people.apache.org/~jacques/apache-drill-0.5.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc1 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc2 (pending) As you can see, the rc numbers are only used during the voting process. Once we get approval from the incubator, we drop the rc so that external consumers aren't confused by failed released candidates. Hopefully this satisfies your concerns and you can vote +1 for our release. thanks again for your feedback, Jacques On Sun, Sep 7, 2014 at 5:09 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, Your NOTICE file is missing MIT
Re: September report
On 08-09-14 06:57, Roman Shaposhnik wrote: Hi! it looks like September report is almost done, except the following podlings: * Streams [ ](streams) Matt Franklin [ ](streams) Ate Douma [ ](streams) Craig McClanahan If there's any chance the above mentors can facilitate the report and later sign-off on it would be really appreciated. Hi Roman, I'm sorry about the missing Streams report. The problem here is that the current committers, while pretty much active on Streams itself, still have trouble getting it into their skull and planning to draft up a report themselves, so that we (mentors) can sign it off... Previous reports so far had to be drafted up by the mentors to get it done in time, despite repeated nudges. The last time we warned the committers we would do this no more: part of learning the ropes and working towards graduation is that they also learn to take up this responsibility themselves. Regrettably, they again failed to pick this up and clearly I'm annoyed and disappointed :( Hopefully though this blunder and the fact they should 'fix' this already for the report next month will finally make them realize this is not something they can keep overlooking. To be clear, IMO the Streams committers are actually making good progress with the project itself, so from that perspective I do not think the IPMC has much to be worried about. They just need some spanking to get their act together with respect for the Foundation :) So hopefully this direct feedback will be enough 'spanking' ;) and we'll see a proper report delivered and signed off the next month. Kind regards, Ate Thanks, Roman. P.S. The biggest help with the summary is tracking releases -- so if somebody can help with at least that -- it'll be perfect! - 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: How many podlings are being incubated?
I have fixed what was hopefully the last item in the graduation list, so Celix shouldn't appear in the IPMC reports anymore. Cos On Wed, Sep 03, 2014 at 10:13PM, Konstantin Boudnik wrote: Celix has been graduated, but still need to clear podling. My fault - I've promissed to fix it up and got distructed. Will finishe it before the end of the week. Cos On Sun, Aug 24, 2014 at 01:45PM, Alan D. Cabrera wrote: Lookse like we need to update podling.xml. The August report states 31. My tooling states 33: Argus Aurora BatchEE Blur Brooklyn Celix DataFu DeviceMap Drill Droids Falcon Fleece Flink Hadoop Development Tools Kalumet log4cxx2 MetaModel MRQL NPanday ODF Toolkit Optiq Parquet REEF Ripple Samza Sentry Sirona Slider Storm Streams Twill Usergrid Wave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org signature.asc Description: Digital signature
Re: [VOTE] Apache Drill 0.5.0-incubating release
Well, I was trying to gently ask if there was some way to break the impasse between different versions of the documentation. Obviously you saw one thing and Jacques saw another. But you said what he saw was out of date. How could he tell that? Have you rectified the competing versions of documentation? On Mon, Sep 8, 2014 at 4:27 PM, John D. Ament john.d.am...@gmail.com wrote: Ted, Do you mean more than here: [1]: http://www.apache.org/dev/publishing-maven-artifacts.html [2]: http://www.apache.org/dev/release.html#host-rc On Mon, Sep 8, 2014 at 7:12 PM, Ted Dunning ted.dunn...@gmail.com wrote: Is the new process documented somewhere? On Mon, Sep 8, 2014 at 3:17 PM, sebb seb...@gmail.com wrote: On 7 September 2014 20:31, Jacques Nadeau jacq...@apache.org wrote: As I understand the release guidelines, one is not allowed to put something on dist.apache.org until after a release vote by the Incubator PMC approves that release: Only formally-approved releases may be distributed from the main directories [1] For this candidate, as with our last two releases, we followed this piece of information: It is traditional that release managers use their Apache home space to make available release candidates. [1] Historic tradition; that was before svnpubsub. Note that the DEV tree at https://dist.apache.org/repos/dist/dev/xyz is NOT published to www.apache.org/dist The svnpubsub process takes releases from the RELEASE tree at https://dist.apache.org/repos/dist/release/xyz Since they have the same parent, one can use svn move (or svnmucc) to transfer the files from dev to release area. This provides traceability (assuming the the release vote includes the SVN revision number) To date, we only push to dist.apache.org once we have received approval here. Can you point me to the guidelines that lead you to believe that this must be staged on dist.apache.org? Thanks, Jacques [1] http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote On Sun, Sep 7, 2014 at 11:48 AM, John D. Ament john.d.am...@gmail.com wrote: Sorry, I have to vote -1 The release is not staged in the proper place (e.g. https://dist.apache.org/repos/dist/dev/incubator/ ) If this gets moved, I can vote +1 On Sun, Sep 7, 2014 at 11:29 AM, Jacques Nadeau jacq...@apache.org wrote: Hi John, Thanks for the feedback. I'd like to respond to each of your concerns: Your NOTICE file is missing MIT license. The notice file states: Please see LICENSE for additional copyright and licensing information. The LICENSE file contains the MIT license. Your source file includes binaries in the sample-data directory. These are small sample data files that are used to do various unit tests. They have been approved on both of our previous releases because of their small size (24k combined) and the fact that they are not source code. These are raw data files that happen to be binary in nature but are for all purposes the same as example json files we include for testing purposes. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) The name of the release candidate directory is due to the nature of the Apache voting process. Each time we have a release candidate in the community, we hold a vote. We always maintain past release candidates so that we can refer back to them. All artifacts in the release candidate hold the release/public names and will ultimately be hosted on the Apache distribution servers at the appropriately named release directory. For historical perspective on this, see the following that has been our strategy thus far: our m1 release: http://people.apache.org/~jacques/apache-drill-1.0.0-m1 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc2 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc3 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4 (approved) -- and distributed as https://archive.apache.org/dist/incubator/drill/drill-1.0.0-m1-incubating/ our 0.4.0 release: http://people.apache.org/~jacques/apache-drill-0.4.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.4.0.rc1 (approved) -- distributed as https://archive.apache.org/dist/incubator/drill/drill-0.4.0-incubating/ our 0.5.0 release: http://people.apache.org/~jacques/apache-drill-0.5.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc1 (fail)
Re: [VOTE] Apache Drill 0.5.0-incubating release
John, Actually, on reading the links you provide, neither provides solid guidance about the issue in question. The second link comes closest where it says that projects typically use one of three different methods. How does this document your strong preference for a single one of these alternatives? On Mon, Sep 8, 2014 at 4:27 PM, John D. Ament john.d.am...@gmail.com wrote: Ted, Do you mean more than here: [1]: http://www.apache.org/dev/publishing-maven-artifacts.html [2]: http://www.apache.org/dev/release.html#host-rc On Mon, Sep 8, 2014 at 7:12 PM, Ted Dunning ted.dunn...@gmail.com wrote: Is the new process documented somewhere? On Mon, Sep 8, 2014 at 3:17 PM, sebb seb...@gmail.com wrote: On 7 September 2014 20:31, Jacques Nadeau jacq...@apache.org wrote: As I understand the release guidelines, one is not allowed to put something on dist.apache.org until after a release vote by the Incubator PMC approves that release: Only formally-approved releases may be distributed from the main directories [1] For this candidate, as with our last two releases, we followed this piece of information: It is traditional that release managers use their Apache home space to make available release candidates. [1] Historic tradition; that was before svnpubsub. Note that the DEV tree at https://dist.apache.org/repos/dist/dev/xyz is NOT published to www.apache.org/dist The svnpubsub process takes releases from the RELEASE tree at https://dist.apache.org/repos/dist/release/xyz Since they have the same parent, one can use svn move (or svnmucc) to transfer the files from dev to release area. This provides traceability (assuming the the release vote includes the SVN revision number) To date, we only push to dist.apache.org once we have received approval here. Can you point me to the guidelines that lead you to believe that this must be staged on dist.apache.org? Thanks, Jacques [1] http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote On Sun, Sep 7, 2014 at 11:48 AM, John D. Ament john.d.am...@gmail.com wrote: Sorry, I have to vote -1 The release is not staged in the proper place (e.g. https://dist.apache.org/repos/dist/dev/incubator/ ) If this gets moved, I can vote +1 On Sun, Sep 7, 2014 at 11:29 AM, Jacques Nadeau jacq...@apache.org wrote: Hi John, Thanks for the feedback. I'd like to respond to each of your concerns: Your NOTICE file is missing MIT license. The notice file states: Please see LICENSE for additional copyright and licensing information. The LICENSE file contains the MIT license. Your source file includes binaries in the sample-data directory. These are small sample data files that are used to do various unit tests. They have been approved on both of our previous releases because of their small size (24k combined) and the fact that they are not source code. These are raw data files that happen to be binary in nature but are for all purposes the same as example json files we include for testing purposes. Ideally, your directory name should match the release version (0.5.0.rc2 vs 0.5.0) The name of the release candidate directory is due to the nature of the Apache voting process. Each time we have a release candidate in the community, we hold a vote. We always maintain past release candidates so that we can refer back to them. All artifacts in the release candidate hold the release/public names and will ultimately be hosted on the Apache distribution servers at the appropriately named release directory. For historical perspective on this, see the following that has been our strategy thus far: our m1 release: http://people.apache.org/~jacques/apache-drill-1.0.0-m1 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc2 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc3 (fail) http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4 (approved) -- and distributed as https://archive.apache.org/dist/incubator/drill/drill-1.0.0-m1-incubating/ our 0.4.0 release: http://people.apache.org/~jacques/apache-drill-0.4.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.4.0.rc1 (approved) -- distributed as https://archive.apache.org/dist/incubator/drill/drill-0.4.0-incubating/ our 0.5.0 release: http://people.apache.org/~jacques/apache-drill-0.5.0.rc0 (fail) http://people.apache.org/~jacques/apache-drill-0.5.0.rc1 (fail)
