Re: [VOTE] Release for Bigtop version 0.1.0-incubating
On Sat, Aug 20, 2011 at 03:08:47AM +0100, sebb wrote: > Archive still contains .gitignore files, which should be excluded. I'm curious: what's the harm in including the .gitignore files? Sure, they serve no practical purpose in a release tarball, but it's nice to have source releases which are file-for-file identical to a version-control tag. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
On 19 August 2011 23:14, Andrew Bayer wrote: > Ack, I screwed up and overwrote RC0 with RC1. In any case, please find RC1 > at http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-1/. NOTICE looks good, and I can see DISCLAIMER. Archive still contains .gitignore files, which should be excluded. > Website should update shortly. No sign yet. > A. > > On Fri, Aug 19, 2011 at 3:00 PM, Andrew Bayer wrote: > >> Oh, and I'm reformatting NOTICE now as well. The .gitignore files - I'll >> open a bug to remove the top-level one from the tarball, but the ones that >> show up deeper are expected by the build process. >> >> A. >> >> >> On Fri, Aug 19, 2011 at 2:58 PM, Andrew Bayer wrote: >> >>> Which source files are missing the headers? I know there are some files >>> without headers, but the ones I know of are that way because they're >>> expected to be in certain formats, they don't allow comments, etc - these >>> should only be Debian/RPM packaging files, unless I'm missing something. >>> >>> As to the package contents - as far as I can tell, everything is under >>> bigtop-0.1.0-incubating. The contents there are the same as in SVN, same >>> layout as in SVN, etc. The content under test is not yet being built/used, >>> and may well be reorganized later, but it's all there. If there are any >>> inconsistencies with what's in SVN, let me know and I'll check it out. >>> >>> Adding DISCLAIMER now. >>> >>> A. >>> >>> >>> On Fri, Aug 19, 2011 at 2:48 PM, sebb wrote: >>> On 19 August 2011 19:25, Andrew Bayer wrote: > This is the first incubator release for Apache Bigtop, version > 0.1.0-incubating. > > It fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 > > *** Please download, test, and vote by Wednesday, August 24 (3 working days > from now) > > Note that we are voting on the source (tag). > > Source tarball, checksums, signature: > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ A lot of source files don't have any license headers. There's no DISCLAIMER in the archive; needs also to be added to SVN alongside NOTICE and LICENSE. The DISCLAIMER text must also be prominently displayed on the bigtop website. IMO these must be fixed before a release. The NOTICE file has a slightly different layout from normal (not a blocker). It would look better if the paragraph were wrapped after "developed at" - as is normally done - because the URL would then not be left dangling. I would not expect the .gitignore files to be included in the source release. There seems to be a problem with the packaging of the archive - I would expect all files to be under the top-level directory bigtop-0.1.0-incubating, but there are also parallel directories package, sqoop, smokes etc. This makes it very difficult to check the archive against the source archive. Again, I think this needs to be fixed before release. > The tag to be voted on: > http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating > Bigtop's KEYS file, containing the PGP keys used to sign the release: > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS sig is OK > Note that the Incubator PMC needs to vote on the release after a successful > PPMC vote before any release can be made official. > > Thanks! > > A. > - 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 for Bigtop version 0.1.0-incubating
On 19 August 2011 22:58, Andrew Bayer wrote: > Which source files are missing the headers? I know there are some files > without headers, but the ones I know of are that way because they're > expected to be in certain formats, they don't allow comments, etc - these > should only be Debian/RPM packaging files, unless I'm missing something. There are several shell scripts, e.g. hadoop-pig.postinst hadoop-pig.preinst src/pkg/deb/pig/rules Other files that could and should have AL headers: *.apt SQL scripts such as test/src/smokes/hive/src/test/resources/scripts/integration/hbase_joins/in (it would not harm to include a description as well) There may be others. I suggest running RAT to produce a report. > As to the package contents - as far as I can tell, everything is under > bigtop-0.1.0-incubating. The contents there are the same as in SVN, same > layout as in SVN, etc. The content under test is not yet being built/used, > and may well be reorganized later, but it's all there. If there are any > inconsistencies with what's in SVN, let me know and I'll check it out. There seems to a problem with reading the tar file using Winzip (and in fact with Ant as well, which is what I use normally for command-line unpacking). Some of the paths are missing some leading segments. I just tried using 7-Zip and that worked fine. The archive matches the SVN tag once the unpacking is sorted out. What exact command did you use to create the tar file? It's clearly creating a file that confuses Winzip and Ant. Maybe you can try using Ant to unpack the archive and see if you see the same behaviour: I'm using Ant 1.8.2 on WinXP > Adding DISCLAIMER now. > > A. > > On Fri, Aug 19, 2011 at 2:48 PM, sebb wrote: > >> On 19 August 2011 19:25, Andrew Bayer wrote: >> > This is the first incubator release for Apache Bigtop, version >> > 0.1.0-incubating. >> > >> > It fixes the following issues: >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 >> > >> > *** Please download, test, and vote by Wednesday, August 24 (3 working >> days >> > from now) >> > >> > Note that we are voting on the source (tag). >> > >> > Source tarball, checksums, signature: >> > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ >> >> A lot of source files don't have any license headers. >> There's no DISCLAIMER in the archive; needs also to be added to SVN >> alongside NOTICE and LICENSE. >> >> The DISCLAIMER text must also be prominently displayed on the bigtop >> website. >> >> IMO these must be fixed before a release. >> >> The NOTICE file has a slightly different layout from normal (not a >> blocker). >> It would look better if the paragraph were wrapped after "developed >> at" - as is normally done - because the URL would then not be left >> dangling. >> >> I would not expect the .gitignore files to be included in the source >> release. >> >> There seems to be a problem with the packaging of the archive - I >> would expect all files to be under the top-level directory >> bigtop-0.1.0-incubating, but there are also parallel directories >> package, sqoop, smokes etc. This makes it very difficult to check the >> archive against the source archive. >> >> Again, I think this needs to be fixed before release. >> >> > The tag to be voted on: >> > >> http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating >> >> > Bigtop's KEYS file, containing the PGP keys used to sign the release: >> > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS >> >> sig is OK >> >> > Note that the Incubator PMC needs to vote on the release after a >> successful >> > PPMC vote before any release can be made official. >> > >> > Thanks! >> > >> > A. >> > >> >> - >> 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
[PROPOSAL] HMS Project for the Apache Incubator
Greetings All, We would like to propose HMS Project for inclusion in ASF Incubator as a new podling. HMS is monitoring, administration and lifecycle management project for Apache Hadoop clusters. The complete proposal can be found at: http://wiki.apache.org/incubator/HMSProposal The initial contents of this proposal are also pasted below for convenience. Thanks and Regards, Eric = HMS Proposal = == Abstract == HMS is monitoring, administration and lifecycle management project for Apache Hadoop clusters. == Proposal == HMS will simplify the process of deployment, configuration, management and monitoring of the collection of Hadoop services and applications that compose a Hadoop cluster. The collection of services (Hadoop Stack) will include at least HDFS, !MapReduce, HBase, Hive, HCatalog, Pig and Zookeeper. HMS will be easily configurable to add additional services and applications to the stack. Our plan is to support the Hadoop stack as a unit of deployment and configuration where only certain pre-tested versions of software components are supported to be part of Hadoop stack. Administrators can always enable/disable the individual software components from the Hadoop stack per their deployment needs. The main use cases that HMS is trying to address are the following: * Hadoop stack deployment and upgrades * Hadoop services configuration & management * Administration of Hadoop services * Includes starting and stopping services * Hadoop system maintenance tasks, such as fsck, format, re-balance, and compaction * User access & quota management on Hadoop clusters * Easily check and be alerted to failures in Hadoop servers * Automated discovery of new machines that become available * Expanding and contracting Hadoop clusters * Automatic resynchronization to ‘desired’ state (of Hadoop stack) to handle faulty nodes * Handle node burn-ins (stress test nodes using Hadoop before deploying them for production use) * Simple monitoring and management UI * Dynamic configuration - Hadoop configuration deduced from machine attributes (e.g., RAM, CPU, Disk) * Operational HBase-based (inspired by OpenTSDB) monitoring for Hadoop clusters * Make it possible for administrators to deploy other Hadoop related services and client applications HMS is targeted to administrators responsible for managing Hadoop clusters. HMS leverages existing data center management and monitoring infrastructure - Nagios, LDAP, Kerberos, etc. All HMS functionality and data will be accessible via RESTFUL APIs and command line tools to facilitate its integration with existing data center management suites. For the bare metal provisioning, the cluster admins continue to use their existing infrastructure. Provisioning a machine from scratch is not in the scope of the current roadmap. == Background == Hadoop’s ecosystem includes many projects (HDFS, !MapReduce, Pig, HBase, etc.). In many cases, users and operators typically want to deploy a combination of some projects as a stack. It takes a significant amount of time to get a properly configured Hadoop cluster up and running. HMS has been designed to solve that problem. HMS automates the whole process of deploying a stack. HMS is being developed by developers employed with Yahoo!, Hortonworks and IBM. Such a tool would have a large number of users and increase the adoption of Apache Hadoop’s ecosystem. We are therefore proposing to make HMS Apache open source. == Rationale == Hadoop clusters are complicated and difficult to deploy and manage. The HMS project aims to improve the usability of Apache Hadoop. Doing so will demoncratize Apache Hadoop, growing its community and increasing the places Hadoop can be used and the problems it can solve. By developing HMS in Apache we hope to gather a diverse community of contributors, helping to make sure that HMS is deployable in as many different situations as possible. members of the Hadoop development community will be able to influence HMS’s roadmap, and contribute to it. We believe having HMS as part of the Apache Hadoop ecosystem will be a great benefit to all of Hadoop's users. == Current Status == Prototype available, developed by the list of initial committers. === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around HMS following the Apache meritocracy model. We have wanted to make the project open source and encourage contributors from multiple organizations from the start. We plan to provide plenty of support to new developers and to quickly recruit those who make solid contributions to committer status. === Community === We are happy to report that multiple organizations are already represented by initial team. We hope to extend the user and developer base further in the future and build a solid open source community around HMS. === Core Developers === HMS is currently being developed by four engineers from Hortonworks - Eric Yang, Owen O’Ma
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
Ack, I screwed up and overwrote RC0 with RC1. In any case, please find RC1 at http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-1/. Website should update shortly. A. On Fri, Aug 19, 2011 at 3:00 PM, Andrew Bayer wrote: > Oh, and I'm reformatting NOTICE now as well. The .gitignore files - I'll > open a bug to remove the top-level one from the tarball, but the ones that > show up deeper are expected by the build process. > > A. > > > On Fri, Aug 19, 2011 at 2:58 PM, Andrew Bayer wrote: > >> Which source files are missing the headers? I know there are some files >> without headers, but the ones I know of are that way because they're >> expected to be in certain formats, they don't allow comments, etc - these >> should only be Debian/RPM packaging files, unless I'm missing something. >> >> As to the package contents - as far as I can tell, everything is under >> bigtop-0.1.0-incubating. The contents there are the same as in SVN, same >> layout as in SVN, etc. The content under test is not yet being built/used, >> and may well be reorganized later, but it's all there. If there are any >> inconsistencies with what's in SVN, let me know and I'll check it out. >> >> Adding DISCLAIMER now. >> >> A. >> >> >> On Fri, Aug 19, 2011 at 2:48 PM, sebb wrote: >> >>> On 19 August 2011 19:25, Andrew Bayer wrote: >>> > This is the first incubator release for Apache Bigtop, version >>> > 0.1.0-incubating. >>> > >>> > It fixes the following issues: >>> > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 >>> > >>> > *** Please download, test, and vote by Wednesday, August 24 (3 working >>> days >>> > from now) >>> > >>> > Note that we are voting on the source (tag). >>> > >>> > Source tarball, checksums, signature: >>> > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ >>> >>> A lot of source files don't have any license headers. >>> There's no DISCLAIMER in the archive; needs also to be added to SVN >>> alongside NOTICE and LICENSE. >>> >>> The DISCLAIMER text must also be prominently displayed on the bigtop >>> website. >>> >>> IMO these must be fixed before a release. >>> >>> The NOTICE file has a slightly different layout from normal (not a >>> blocker). >>> It would look better if the paragraph were wrapped after "developed >>> at" - as is normally done - because the URL would then not be left >>> dangling. >>> >>> I would not expect the .gitignore files to be included in the source >>> release. >>> >>> There seems to be a problem with the packaging of the archive - I >>> would expect all files to be under the top-level directory >>> bigtop-0.1.0-incubating, but there are also parallel directories >>> package, sqoop, smokes etc. This makes it very difficult to check the >>> archive against the source archive. >>> >>> Again, I think this needs to be fixed before release. >>> >>> > The tag to be voted on: >>> > >>> http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating >>> >>> > Bigtop's KEYS file, containing the PGP keys used to sign the release: >>> > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS >>> >>> sig is OK >>> >>> > Note that the Incubator PMC needs to vote on the release after a >>> successful >>> > PPMC vote before any release can be made official. >>> > >>> > Thanks! >>> > >>> > A. >>> > >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> >
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
Oh, and I'm reformatting NOTICE now as well. The .gitignore files - I'll open a bug to remove the top-level one from the tarball, but the ones that show up deeper are expected by the build process. A. On Fri, Aug 19, 2011 at 2:58 PM, Andrew Bayer wrote: > Which source files are missing the headers? I know there are some files > without headers, but the ones I know of are that way because they're > expected to be in certain formats, they don't allow comments, etc - these > should only be Debian/RPM packaging files, unless I'm missing something. > > As to the package contents - as far as I can tell, everything is under > bigtop-0.1.0-incubating. The contents there are the same as in SVN, same > layout as in SVN, etc. The content under test is not yet being built/used, > and may well be reorganized later, but it's all there. If there are any > inconsistencies with what's in SVN, let me know and I'll check it out. > > Adding DISCLAIMER now. > > A. > > > On Fri, Aug 19, 2011 at 2:48 PM, sebb wrote: > >> On 19 August 2011 19:25, Andrew Bayer wrote: >> > This is the first incubator release for Apache Bigtop, version >> > 0.1.0-incubating. >> > >> > It fixes the following issues: >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 >> > >> > *** Please download, test, and vote by Wednesday, August 24 (3 working >> days >> > from now) >> > >> > Note that we are voting on the source (tag). >> > >> > Source tarball, checksums, signature: >> > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ >> >> A lot of source files don't have any license headers. >> There's no DISCLAIMER in the archive; needs also to be added to SVN >> alongside NOTICE and LICENSE. >> >> The DISCLAIMER text must also be prominently displayed on the bigtop >> website. >> >> IMO these must be fixed before a release. >> >> The NOTICE file has a slightly different layout from normal (not a >> blocker). >> It would look better if the paragraph were wrapped after "developed >> at" - as is normally done - because the URL would then not be left >> dangling. >> >> I would not expect the .gitignore files to be included in the source >> release. >> >> There seems to be a problem with the packaging of the archive - I >> would expect all files to be under the top-level directory >> bigtop-0.1.0-incubating, but there are also parallel directories >> package, sqoop, smokes etc. This makes it very difficult to check the >> archive against the source archive. >> >> Again, I think this needs to be fixed before release. >> >> > The tag to be voted on: >> > >> http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating >> >> > Bigtop's KEYS file, containing the PGP keys used to sign the release: >> > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS >> >> sig is OK >> >> > Note that the Incubator PMC needs to vote on the release after a >> successful >> > PPMC vote before any release can be made official. >> > >> > Thanks! >> > >> > A. >> > >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
Which source files are missing the headers? I know there are some files without headers, but the ones I know of are that way because they're expected to be in certain formats, they don't allow comments, etc - these should only be Debian/RPM packaging files, unless I'm missing something. As to the package contents - as far as I can tell, everything is under bigtop-0.1.0-incubating. The contents there are the same as in SVN, same layout as in SVN, etc. The content under test is not yet being built/used, and may well be reorganized later, but it's all there. If there are any inconsistencies with what's in SVN, let me know and I'll check it out. Adding DISCLAIMER now. A. On Fri, Aug 19, 2011 at 2:48 PM, sebb wrote: > On 19 August 2011 19:25, Andrew Bayer wrote: > > This is the first incubator release for Apache Bigtop, version > > 0.1.0-incubating. > > > > It fixes the following issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 > > > > *** Please download, test, and vote by Wednesday, August 24 (3 working > days > > from now) > > > > Note that we are voting on the source (tag). > > > > Source tarball, checksums, signature: > > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ > > A lot of source files don't have any license headers. > There's no DISCLAIMER in the archive; needs also to be added to SVN > alongside NOTICE and LICENSE. > > The DISCLAIMER text must also be prominently displayed on the bigtop > website. > > IMO these must be fixed before a release. > > The NOTICE file has a slightly different layout from normal (not a > blocker). > It would look better if the paragraph were wrapped after "developed > at" - as is normally done - because the URL would then not be left > dangling. > > I would not expect the .gitignore files to be included in the source > release. > > There seems to be a problem with the packaging of the archive - I > would expect all files to be under the top-level directory > bigtop-0.1.0-incubating, but there are also parallel directories > package, sqoop, smokes etc. This makes it very difficult to check the > archive against the source archive. > > Again, I think this needs to be fixed before release. > > > The tag to be voted on: > > > http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating > > > Bigtop's KEYS file, containing the PGP keys used to sign the release: > > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS > > sig is OK > > > Note that the Incubator PMC needs to vote on the release after a > successful > > PPMC vote before any release can be made official. > > > > Thanks! > > > > A. > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
On 19 August 2011 19:25, Andrew Bayer wrote: > This is the first incubator release for Apache Bigtop, version > 0.1.0-incubating. > > It fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 > > *** Please download, test, and vote by Wednesday, August 24 (3 working days > from now) > > Note that we are voting on the source (tag). > > Source tarball, checksums, signature: > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ A lot of source files don't have any license headers. There's no DISCLAIMER in the archive; needs also to be added to SVN alongside NOTICE and LICENSE. The DISCLAIMER text must also be prominently displayed on the bigtop website. IMO these must be fixed before a release. The NOTICE file has a slightly different layout from normal (not a blocker). It would look better if the paragraph were wrapped after "developed at" - as is normally done - because the URL would then not be left dangling. I would not expect the .gitignore files to be included in the source release. There seems to be a problem with the packaging of the archive - I would expect all files to be under the top-level directory bigtop-0.1.0-incubating, but there are also parallel directories package, sqoop, smokes etc. This makes it very difficult to check the archive against the source archive. Again, I think this needs to be fixed before release. > The tag to be voted on: > http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating > Bigtop's KEYS file, containing the PGP keys used to sign the release: > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS sig is OK > Note that the Incubator PMC needs to vote on the release after a successful > PPMC vote before any release can be made official. > > Thanks! > > A. > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
I'm not sure if I'm supposed to explicitly vote, but just in case: +1 binding A. On Fri, Aug 19, 2011 at 12:53 PM, Andrew Bayer wrote: > Personally, I'm fine with releasing so long as CentOS5 and Ubuntu work - > anything else can be fixed/added in 0.2.0-incubating. > > A. > > > On Fri, Aug 19, 2011 at 11:48 AM, Bruno Mahé wrote: > >> My last patch for centos5 broke openSUSE/Mageia (here lies the troubles >> of having different set of VMs at home and at work). >> I am booting up right now a bunch of VMs to ensure next patch won't >> break anything. >> Could we re-cut a rc after that patch? >> >> >> On 08/19/2011 11:25 AM, Andrew Bayer wrote: >> > This is the first incubator release for Apache Bigtop, version >> > 0.1.0-incubating. >> > >> > It fixes the following issues: >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 >> > >> > *** Please download, test, and vote by Wednesday, August 24 (3 working >> days >> > from now) >> > >> > Note that we are voting on the source (tag). >> > >> > Source tarball, checksums, signature: >> > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ >> > >> > The tag to be voted on: >> > >> http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating >> > >> > Bigtop's KEYS file, containing the PGP keys used to sign the release: >> > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS >> > >> > Note that the Incubator PMC needs to vote on the release after a >> successful >> > PPMC vote before any release can be made official. >> > >> > Thanks! >> > >> > A. >> > >> >> >
Re: [VOTE] Release for Bigtop version 0.1.0-incubating
Personally, I'm fine with releasing so long as CentOS5 and Ubuntu work - anything else can be fixed/added in 0.2.0-incubating. A. On Fri, Aug 19, 2011 at 11:48 AM, Bruno Mahé wrote: > My last patch for centos5 broke openSUSE/Mageia (here lies the troubles > of having different set of VMs at home and at work). > I am booting up right now a bunch of VMs to ensure next patch won't > break anything. > Could we re-cut a rc after that patch? > > > On 08/19/2011 11:25 AM, Andrew Bayer wrote: > > This is the first incubator release for Apache Bigtop, version > > 0.1.0-incubating. > > > > It fixes the following issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 > > > > *** Please download, test, and vote by Wednesday, August 24 (3 working > days > > from now) > > > > Note that we are voting on the source (tag). > > > > Source tarball, checksums, signature: > > http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ > > > > The tag to be voted on: > > > http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating > > > > Bigtop's KEYS file, containing the PGP keys used to sign the release: > > http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS > > > > Note that the Incubator PMC needs to vote on the release after a > successful > > PPMC vote before any release can be made official. > > > > Thanks! > > > > A. > > > >
Re: [VOTE] Release HCatalog 0.1-incubating (RC2)
On 18 August 2011 23:48, Alan Gates wrote: > > On Aug 18, 2011, at 3:30 PM, sebb wrote: >>> >> >> Yes, mostly. >> >> What about JUnit? The archive includes junit 3.8.1 (seems a bit old - >> current version is 4.8.2) >> Also Thrift-Facebook, which has package name com.facebook - suggests >> it is not part of Apache Thrift >> >> Is ANTLR really needed at run-time? Ditto JUnit? >> If it's only need to build the software it can just be listed as a >> requirement in the build instructions. > > Antlr has a runtime jar that we need to ship. And JUnit? >> >> Given that the code appears to use Ivy, this should be able to fetch >> compile-time dependencies automatically. >> >> BTW, you include both log4j 1.2.15 and 1.2.16 which looks wrong. Also >> antlr 2.7.7 and 3.0.1. Mixed jars often cause problems. >> >> Not sure you need both commons-logging and commons-logging-api; also >> latest version is 1.1.1 (released 2007) > > All this stuff is brought along by Hive, not HCatalog unique code, so we're > not in control of the versions, including the multiple versions. Perhaps you shpuld report the issue to Hive then. >> >>> Regarding the LICENSE file the licenses for the 3rd party software is in >>> the Hive's LICENSE file which we include, but we can move it up to the top >>> level LICENSE file. >> >> Yes, all required licenses must be in the top-level LICENSE file. You >> cannot expect users to hunt around looking for LICENSE files. > > We'll fix this. > >> >> I would expect to find a separate source release archive, with just >> the source from the HCatalog project. >> If I want the source, why should I have to download all the binary >> dependencies too? > > No project I've been on so far (Hadoop, Pig) does this. All projects I have been on - Jakarta BSF & JMeter; Commons, HttpComponents; (and many others I use Tomcat) release source-only archives. Most also release binary-only archives. See also http://www.apache.org/dev/release-publishing.html#valid http://www.apache.org/dev/release.html#what-must-every-release-contain >> >> BTW, I don't understand why you include an external to Hive source - >> surely you can just depend on one of the Hive releases? >> > No. HCatalog depends on features that have been added to Hive that are not > yet released. In general, when we set up the project one of the things we > realized was that, due to different points of maturity, Hive and HCatalog are > moving at different speeds. Rather than try to force Hive releases when > HCatalog needs them it makes more sense to include Hive's code in HCatalog. > At some point in the future, as HCatalog matures, I assume this will change > and HCatalog will be able to depend on released versions of Hive. > > Alan. > > > - > 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 Droids 0.1-incubating RC3
On 08/15/2011 01:20 PM, Richard Frovarp wrote: Please vote on the release candidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 4 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201107.mbox/%3c4e31b811.3080...@apache.org%3E Source files: http://people.apache.org/~rfrovarp/droids/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachedroids-008/ SVN source tag (r1151835): https://svn.apache.org/repos/asf/incubator/droids/tags/0.1.0-incubating/ PGP release keys (signed using 3698A2B1): https://svn.apache.org/repos/asf/incubator/droids/KEYS [ ] +1 [ ] +0 [ ] -1 Thanks, Richard Withdrawn. Will perform a new release this weekend that has fixes for the issues found. Richard - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release for Bigtop version 0.1.0-incubating
This is the first incubator release for Apache Bigtop, version 0.1.0-incubating. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549&styleName=Html&projectId=12311420 *** Please download, test, and vote by Wednesday, August 24 (3 working days from now) Note that we are voting on the source (tag). Source tarball, checksums, signature: http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/ The tag to be voted on: http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating Bigtop's KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS Note that the Incubator PMC needs to vote on the release after a successful PPMC vote before any release can be made official. Thanks! A.
Re: [wave] Code grant and IP
I would say it does not mean anything. Projects mailinglist after incubation are for example: d...@wave.apache.org While incubation it might be: wave-...@incubator.apache.org On Fri, Aug 19, 2011 at 7:28 PM, Dave Fisher wrote: > So what does it mean when a committers userid - mine is w...@apache.org == a > project name Apache Wave? > > Not that I have noticed any spam coming to me. > > Regards, > Dave > > On Aug 19, 2011, at 8:42 AM, Christian Grobmeier wrote: > >> Hi Dan, >> >> thanks. I have updated the status page for wave to reflect this. >> >> Cheers >> Christian >> >> On Fri, Aug 19, 2011 at 5:31 PM, Dan Peterson wrote: >>> Hi Christian, >>> >>> Yes, the Google Wave --> ASF code grant is covered. >>> >>> On 22 December 2010 I (dpeter...@google.com) submitted the appropriate >>> materials for the grant from Google to Apache (secret...@apache.org). Less >>> than 2 hours later, Craig L Russel (craig.russ...@sun.com) acknowledged >>> receipt. >>> >>> Regards, >>> -Dan >>> >>> On Fri, Aug 19, 2011 at 8:05 AM, Christian Grobmeier >>> wrote: >>> At the wave-dev list is currently a discussion on the future of the project. It seems there are some emotions on the svn/hg discussion and other infra related tasks. When I looked at the status page I saw some very import items are deleted: http://incubator.apache.org/projects/wave.html Now I have found the discussion if all committer clas are on file: http://bit.ly/rqf3Gu At it seems it is. But I have not found anything if there is an actual code grant from Google to donate Wave to Apache. Can somebody look into the holy archive of grants and let me know if the code grant has been received? Thanks, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> >> >> -- >> http://www.grobmeier.de >> >> - >> 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 > > -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [wave] Code grant and IP
So what does it mean when a committers userid - mine is w...@apache.org == a project name Apache Wave? Not that I have noticed any spam coming to me. Regards, Dave On Aug 19, 2011, at 8:42 AM, Christian Grobmeier wrote: > Hi Dan, > > thanks. I have updated the status page for wave to reflect this. > > Cheers > Christian > > On Fri, Aug 19, 2011 at 5:31 PM, Dan Peterson wrote: >> Hi Christian, >> >> Yes, the Google Wave --> ASF code grant is covered. >> >> On 22 December 2010 I (dpeter...@google.com) submitted the appropriate >> materials for the grant from Google to Apache (secret...@apache.org). Less >> than 2 hours later, Craig L Russel (craig.russ...@sun.com) acknowledged >> receipt. >> >> Regards, >> -Dan >> >> On Fri, Aug 19, 2011 at 8:05 AM, Christian Grobmeier >> wrote: >> >>> At the wave-dev list is currently a discussion on the future of the >>> project. It seems there are some emotions on the svn/hg discussion and >>> other infra related tasks. >>> >>> When I looked at the status page I saw some very import items are deleted: >>> http://incubator.apache.org/projects/wave.html >>> >>> Now I have found the discussion if all committer clas are on file: >>> http://bit.ly/rqf3Gu >>> At it seems it is. >>> >>> But I have not found anything if there is an actual code grant from >>> Google to donate Wave to Apache. Can somebody look into the holy >>> archive of grants and let me know if the code grant has been received? >>> >>> Thanks, >>> Christian >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> > > > > -- > http://www.grobmeier.de > > - > 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 Droids 0.1-incubating RC3
On 08/17/2011 12:49 PM, sebb wrote: On 17 August 2011 18:35, Richard Frovarp wrote: I fully get your point, but they do. One can find everything here: https://repository.apache.org/content/repositories/orgapachedroids-008/org/apache/droids/droids/0.1.0-incubating/ In the future, is there anything wrong with pointing to the Maven staging repo for the source release part of this? Convention shows that people put it in their home directories. I simply just did a wget of the one file and forgot to grab the sigs and hashes. I can grab everything, but just pointing to the staging directory would be simpler. Yes, that would be fine, but you provided the URL for review, which is what I did. I've not yet looked at the Maven artifacts in any detail. Yeah, I understand that. Just trying to figure out how to proceed for the next time around. Thanks. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release HCatalog 0.1-incubating (RC2)
On Aug 18, 2011, at 3:30 PM, sebb wrote: >> > > Yes, mostly. > > What about JUnit? The archive includes junit 3.8.1 (seems a bit old - > current version is 4.8.2) > Also Thrift-Facebook, which has package name com.facebook - suggests > it is not part of Apache Thrift > > Is ANTLR really needed at run-time? Ditto JUnit? > If it's only need to build the software it can just be listed as a > requirement in the build instructions. Antlr has a runtime jar that we need to ship. > > Given that the code appears to use Ivy, this should be able to fetch > compile-time dependencies automatically. > > BTW, you include both log4j 1.2.15 and 1.2.16 which looks wrong. Also > antlr 2.7.7 and 3.0.1. Mixed jars often cause problems. > > Not sure you need both commons-logging and commons-logging-api; also > latest version is 1.1.1 (released 2007) All this stuff is brought along by Hive, not HCatalog unique code, so we're not in control of the versions, including the multiple versions. > >> Regarding the LICENSE file the licenses for the 3rd party software is in the >> Hive's LICENSE file which we include, but we can move it up to the top level >> LICENSE file. > > Yes, all required licenses must be in the top-level LICENSE file. You > cannot expect users to hunt around looking for LICENSE files. We'll fix this. > > I would expect to find a separate source release archive, with just > the source from the HCatalog project. > If I want the source, why should I have to download all the binary > dependencies too? No project I've been on so far (Hadoop, Pig) does this. > > BTW, I don't understand why you include an external to Hive source - > surely you can just depend on one of the Hive releases? > No. HCatalog depends on features that have been added to Hive that are not yet released. In general, when we set up the project one of the things we realized was that, due to different points of maturity, Hive and HCatalog are moving at different speeds. Rather than try to force Hive releases when HCatalog needs them it makes more sense to include Hive's code in HCatalog. At some point in the future, as HCatalog matures, I assume this will change and HCatalog will be able to depend on released versions of Hive. Alan. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
