Re: [VOTE][PROPOSAL] EasyAnt incubator
[X] +1 to accept EasyAnt into the Incubator [] 0 don't care [] -1 object and reason why. Cheers Daniel On Mon, Jan 24, 2011 at 6:14 PM, Antoine Levy-Lambert anto...@gmx.de wrote: I would like to present for a vote the following proposal to be sponsored by the Ant PMC for a new EasyAnt podling. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/EasyAntProposal [] +1 to accept EasyAnt into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Antoine Levy-Lambert --- Proposal text from the wiki --- EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. = Abstract = Easyant is a build system based on Apache Ant and Apache Ivy. = Proposal = EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. = Rationale = On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! = Current Status = == Meritocracy == Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. == Community == EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. == Core Developers == Xavier Hanin and Nicolas Lalev ¡ ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge (http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. == Alignment == EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) = Known risks = == Orphaned products == Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. == Inexperience with Open Source == Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. == Homogenous Developers == The existing committers are spread over a number of countries and employers. == Reliance on Salaried Developers == None of the developers rely on EasyAnt for consulting work. == Relationships with Other Apache Products == As already stated
[VOTE] Release Apache Chemistry cmislib 0.4 incubating
Incubator PMC members, The cmislib sub-project of Apache Chemistry is ready for its first release since joining the Chemistry project. On behalf of the Chemistry dev team, I'd like to ask your approval to release the packages referenced below as Chemistry cmislib 0.4 incubating. The release has passed the Chemistry PMC vote: http://bit.ly/eqXU2X During the vote, 1 IPMC vote was collected (Nick Burch), so we need 2 more IPMC +1 votes to proceed with the release. You can find the main release candidate artifacts (for distribution at apache.org/dist) at: http://people.apache.org/~jpotts/chemistry/cmislib/0.4/dist These artifacts represent what is currently in cmislib head. The vote is open for 72 hours so please cast your votes! [ ] +1 Release this package as Apache Chemistry cmislib 0.4 incubating [ ] -1 Do not release this package because... Thanks, Jeff
Re: [VOTE] Release Apache ManifoldCF 0.1 incubating, RC8
+1 (binding), just as voted on ManifoldCF. -Grant On Jan 20, 2011, at 9:48 PM, Karl Wright wrote: Calling the official vote for release of ManifoldCF 0.1 incubating, RC8, which can be found at http://people.apache.org/~kwright . The community has voted for release of the new RC, so we're ready to go ahead with an incubator vote on the same. Thanks in advance! Karl - 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: [PROPOSAL] Lucene.Net return to the Incubator
Troy, If you have the proposal done, the next thing to do would be to call a vote to accept it. -Grant On Jan 20, 2011, at 8:55 AM, Stefan Bodewig wrote: On 2011-01-18, Troy Howard wrote: If I recall correctly we need at least two mentors before the Incubator PMC can vote on our proposal. Is there anyone else willing to help us out as Mentor? Yes, me. I've just added my name to the propsal page. Stefan - 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: [PROPOSAL] Lucene.Net return to the Incubator
Although, it does look like you need one more Mentor. On Jan 12, 2011, at 5:43 PM, Troy Howard wrote: All, Please review our proposal for moving the Lucene.Net project back to the Incubator. Lucene.Net is currently a Lucene sub-project, however, for reasons detailed in the proposal and various mailing list discussions, we have decided that a move back to the Incubator, with the intent of future graduation as a TLP is the best for the Lucene.Net project. We are pleased to say that Grant Ingersoll has agreed to be our Champion for this proposal, however we are still in need of Mentors from the Incubator community. We'd appreciate help from anyone who is interested. The proposal, in raw text form follows this email and the wiki is located here: http://wiki.apache.org/incubator/Lucene.Net%20Proposal Thanks, Troy Howard = FINAL = 'Subitted on Wednesday, January 12th, 2011' = Lucene.Net - A .NET port of Lucene = == Preface == Lucene.Net is a sub-project which is being spun off from the Lucene TLP but is not yet ready for graduation. We propose to address certain needs of the project by transitioning to an Incubator Podling. == Abstract == Lucene.Net will be a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Proposal == Lucene.Net has three aims. First, it will maintain the existing line-by-line port from Java to C#, fully automating and commoditizing the process such that the project can easily synchronize with the Java Lucene release schedule. Second, it will be a high-performance C# search engine library. Third, it will maximize its usability and power when used within the .NET runtime. To that end, it will present a highly idiomatic, carefully tailored API that takes advantage of many of the special features of the .NET runtime. == Background == Lucene.Net, began as a independent project focused on creating a line-by-line, API for API port of Java Lucene to C#. It continued successfully in this way and eventually became a ASF Incubator project in April of 2006 and graduated as a sub-project of Lucene in October of 2009. The last year has been challenging for the project. The committers who originally lead the project have stopped maintaining it and development has stagnated since June of 2010. The user community has spoken out requesting a change in philosophy and direction for the project, but those requests have been unheeded. This has led to a number of forks outside of the ASF. We would like to bring those forks back in as branches and be responsive to the needs of community without the need for multiple non-ASF forks. The Lucene PMC wants to see the project continue to thrive and has indicated that a return to the Incubator is an appropriate step, with the end goal to build of building a new team of committers and maintaining a steady release cycle meeting the previously stated goals. Because Lucene is working to move away from being an umbrella project, a long term goal of the Lucene.Net project is to graduate to an ASF TLP. == Rationale == There is great need for a search engine library in the mode of Lucene within the .NET runtime. Individuals naturally wish to code in their language of choice. Organizations which do not have significant Java expertise may not want to support Java strictly for the sake of running a Lucene installation. Developers may want to take advantage of C#'s unique language features and the .NET runtime's unique execution and interoperability model. Lucene.Net will meet all these demands. Apache is a natural home for our project given the way it has always operated: user-driven innovation, lively and amiable mailing list discussions, strength through diversity, and so on. We feel comfortable here, and we believe that we will become exemplary Apache citizens. == Initial Goals (to be completed before Feb 2011) == * Build a new list of committers * Make a 2.9.2 compatible release as quickly as possible (this already exists, it just needs to be packaged correctly) * Update website, documentation, etc. * Create a well documented repeatable and fully automated language porting process * Start a .NET style API branch, either by incorporating some or all existing fork projects or by starting a new branch to this end == Current Status == === Meritocracy === We understand meritocracy and will fully embrace this concept in our project management methodology. One of the proposed committers, DIGY, has been a committer on the current Lucene.Net project since November 2008. Prescott Nasser has been a contributor on the project, submitting patches, documentation, and website enhancements. Three of the other proposed initial committers, Troy Howard, Chris Currens and Sergey Mirvoda are both already actively involved in other open source projects, either as committers of code
Re: [VOTE] Release Apache ManifoldCF 0.1 incubating, RC8
Hi Karl, +1 from me (binding). Signatures check out: [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --import *.KEYS gpg: key 03824582: Karl David Wright (CODE SIGNING KEY) kwri...@apache.org not changed gpg: key FE045966: Grant Ingersoll (CODE SIGNING KEY) gsing...@apache.org not changed gpg: Total number processed: 2 gpg: unchanged: 2 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-bin.tar.gz.asc gpg: Signature made Tue Jan 11 14:19:16 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-bin.zip.asc gpg: Signature made Tue Jan 11 14:19:07 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-src.tar.gz.asc gpg: Signature made Tue Jan 11 14:18:59 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-src.zip.asc gpg: Signature made Tue Jan 11 14:18:41 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% cat *.md5 C7CA5B01ADC5A785F63ED559169B4390 *apache-manifoldcf-0.1-incubating-bin.tar.gz CF1744BF9ACF2EFD17F705A875691B02 *apache-manifoldcf-0.1-incubating-bin.zip D134D3F1D01060F2B6800FB19572A576 *apache-manifoldcf-0.1-incubating-src.tar.gz BA2F388B9AF5E66FC0F1437C98EDF846 *apache-manifoldcf-0.1-incubating-src.zip [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% md5sum *-bin*.tar.gz *-bin*.zip *-src*.tar.gz *-src*.zip c7ca5b01adc5a785f63ed559169b4390 apache-manifoldcf-0.1-incubating-bin.tar.gz cf1744bf9acf2efd17f705a875691b02 apache-manifoldcf-0.1-incubating-bin.zip d134d3f1d01060f2b6800fb19572a576 apache-manifoldcf-0.1-incubating-src.tar.gz ba2f388b9af5e66fc0f1437c98edf846 apache-manifoldcf-0.1-incubating-src.zip [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% Thanks for including CHANGES.txt and KEYS. That really helped. Great job and great working the process! Cheers, Chris On Jan 24, 2011, at 9:54 PM, Karl Wright wrote: Oh, forgot to mention that the release candidate tag is at: http://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.1-incubating-RC8/ Karl On Thu, Jan 20, 2011 at 9:48 PM, Karl Wright daddy...@gmail.com wrote: Calling the official vote for release of ManifoldCF 0.1 incubating, RC8, which can be found at http://people.apache.org/~kwright . The community has voted for release of the new RC, so we're ready to go ahead with an incubator vote on the same. Thanks in advance! Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE][PROPOSAL] EasyAnt incubator
+1 Doug On 01/24/2011 09:14 AM, Antoine Levy-Lambert wrote: I would like to present for a vote the following proposal to be sponsored by the Ant PMC for a new EasyAnt podling. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/EasyAntProposal [] +1 to accept EasyAnt into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Antoine Levy-Lambert --- Proposal text from the wiki --- EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. = Abstract = Easyant is a build system based on Apache Ant and Apache Ivy. = Proposal = EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. = Rationale = On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! = Current Status = == Meritocracy == Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. == Community == EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. == Core Developers == Xavier Hanin and Nicolas Lalev�¡�ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge (http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. == Alignment == EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) = Known risks = == Orphaned products == Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. == Inexperience with Open Source == Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. == Homogenous Developers == The existing committers are spread over a number of countries and employers. == Reliance on Salaried Developers == None of the developers rely on EasyAnt for consulting work. == Relationships with Other Apache Products == As already stated above, EasyAnt is intended to have a quite good integration with both Apache Ant and Apache Ivy. == A Excessive Fascination with the Apache Brand == As we're already based on many Apache project (Ant + Ivy),
Re: [VOTE][PROPOSAL] EasyAnt incubator
+1 Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE][PROPOSAL] EasyAnt incubator
+1 (non binding) Xavier On Mon, Jan 24, 2011 at 18:14, Antoine Levy-Lambert anto...@gmx.de wrote: I would like to present for a vote the following proposal to be sponsored by the Ant PMC for a new EasyAnt podling. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/EasyAntProposal [] +1 to accept EasyAnt into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Antoine Levy-Lambert --- Proposal text from the wiki --- EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. = Abstract = Easyant is a build system based on Apache Ant and Apache Ivy. = Proposal = EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. = Rationale = On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! = Current Status = == Meritocracy == Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. == Community == EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. == Core Developers == Xavier Hanin and Nicolas Lalev ¡ ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge ( http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. == Alignment == EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) = Known risks = == Orphaned products == Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. == Inexperience with Open Source == Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. == Homogenous Developers == The existing committers are spread over a number of countries and employers. == Reliance on Salaried Developers == None of the developers rely on EasyAnt for consulting work. == Relationships with Other Apache Products == As already stated above, EasyAnt is intended to have a quite good integration with both
[VOTE] Release Whirr version 0.3.0-incubating
This is the third incubator release for Apache Whirr, version 0.3.0-incubating. We already received one binding IPMC +1 vote for the PPMC release vote on whirr-dev, so are looking for two more. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-whirr-dev/201101.mbox/%3caanlktikdg83pbi+71pj0zcxs7pe_rs4musfavcwnx...@mail.gmail.com%3E The issues fixed for 0.3.0-incubating https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315487styleName=HtmlprojectId=1230 Source and binary files: http://people.apache.org/~tomwhite/whirr-0.3.0-incubating-candidate-0 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-065 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.3.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS The vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Tom - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
