Re: [VOTE]: Buildr 1.3.2 release
Looks ok to me so +1. Would be helpful to include a RAT report with the request, but I ran it myself and it didn't highlight any issues. If the doc pdf is going to be distributed separately it should probably include the Incubator disclaimer text, maybe on the page which already has the Apache License text. ...ant On Mon, Jul 21, 2008 at 9:36 PM, Assaf Arkin [EMAIL PROTECTED] wrote: Up for vote, the Buildr 1.3.2 release. The release vote passed within the PPMC with +3 (+5 including non-binding votes) and no -1: http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/[EMAIL PROTECTED] We're voting on the source distributions available here: http://people.apache.org/~assaf/buildr/1.3.2/distro/http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/ Specifically: http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgzhttp://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.ziphttp://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip The documentation generated for this release is available here: http://people.apache.org/~assaf/buildr/1.3.2/site/http://people.apache.org/%7Eassaf/buildr/1.3.2/site/ http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdfhttp://people.apache.org/%7Eassaf/buildr/1.3.2/site/buildr.pdf The official specification against which this release was tested: http://people.apache.org/~assaf/buildr/1.3.2/site/specs.htmlhttp://people.apache.org/%7Eassaf/buildr/1.3.2/site/specs.html Changes since 1.3.1: * Added: --prereqs command line argument to show all tasks and their dependencies. You can also follow with regular expression to narrow down the list of tasks. * Changed: Upgraded to Rubyforge 1.0.0. * Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems. * Changed: BUILDR-88 Test classes/resources should come before compile classes/resources so they load up earlier in java classpath. * Changed: BUILDR-102 Update JUnit Version to 4.4. * Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the sources paths. * Fixed: BUILDR-76 Added more specs and fixes to compile task. * Fixed: BUILDR-77 Layout feature not working. * Fixed: BUILDR-79 Remove :source option for Scala compiler * Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon. * Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to load Pageant DLLs when running on JRuby/Windows. * Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include abstract classes. * Fixed: BUILDR-90 Installing from source doesn't work with JRuby. * Fixed: BUILDR-91 When doing a release, buildr should spawn the same version of buildr * Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath. * Fixed: BUILDR-95: Only download Scala test framework artifacts when required * Fixed: BUILDR-100 Directory structure documentation needs updating. * Fixed: Installation instructions updated for RubyGems 1.2.0. Assaf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-79) Update guide: releasing-eclipse-update-site to correct some inaccuracies
Update guide: releasing-eclipse-update-site to correct some inaccuracies Key: INCUBATOR-79 URL: https://issues.apache.org/jira/browse/INCUBATOR-79 Project: Incubator Issue Type: Improvement Reporter: Marshall Schor Priority: Minor Found some inaccuracies in the guide while building an eclipse update site: the location of the urlDigest needs to point to the directory containing the digest.zip, not the digest.zip itself. Add info on using relative urls, as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-79) Update guide: releasing-eclipse-update-site to correct some inaccuracies
[ https://issues.apache.org/jira/browse/INCUBATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated INCUBATOR-79: Attachment: patch.txt Update guide: releasing-eclipse-update-site to correct some inaccuracies Key: INCUBATOR-79 URL: https://issues.apache.org/jira/browse/INCUBATOR-79 Project: Incubator Issue Type: Improvement Reporter: Marshall Schor Priority: Minor Attachments: patch.txt Found some inaccuracies in the guide while building an eclipse update site: the location of the urlDigest needs to point to the directory containing the digest.zip, not the digest.zip itself. Add info on using relative urls, as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Apache UIMA CasEditor-2.2.2-incubating
Hello, please vote again to release the Cas Editor. The first vote was rejected, because the ICU license and notice was missing, this is now fixed, see UIMA-1115. On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release it. The vote thread can be found here: http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg07741.html The release artifacts and the rat reports can be found at: http://people.apache.org/~joern/CasEditor-2.2.2-04/ The Cas Editor originally came to Apache under a software grant. Thanks, Jörn
Re: [PROPOSAL] Tashi
Noel J. Bergman wrote: With respect to Initially, we plan to start with one committer each from Carnegie Mellon and Intel Research, with a Yahoo committer to be determined later, that's awkwardly phrased. It appears to imply a corporate representative doing commits for hidden people, something that we consider to be an anti-pattern. That is not the intent. The intent is for Yahoo! to assign someone to work on this project as a direct contributor. But that person has not yet been identified. Whomever is to be actively involved in development should be on the committer list. If it is just a community of just The Two Michaels, fine, but the wording should be rephrased. +1 If Y! does not name someone soon, then that entry should be removed. A committer from Y! can always be added later, based on merit. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tashi
Doug Cutting wrote: Noel J. Bergman wrote: With respect to Initially, we plan to start with one committer each from Carnegie Mellon and Intel Research, with a Yahoo committer to be determined later, that's awkwardly phrased. It appears to imply a corporate representative doing commits for hidden people, something that we consider to be an anti-pattern. That is not the intent. The intent is for Yahoo! to assign someone to work on this project as a direct contributor. But that person has not yet been identified. Whomever is to be actively involved in development should be on the committer list. If it is just a community of just The Two Michaels, fine, but the wording should be rephrased. +1 If Y! does not name someone soon, then that entry should be removed. A committer from Y! can always be added later, based on merit. No; the entry should be removed now. Yahoo the Company cannot place a reservation on a place at the table for an unnamed body. This is not how the ASF works. Nor are committers expressed as delegates of the institutions the work for/study at. This places a cloud over the acceptance of this particular project, and I would encourage everyone to be sure their mentors/champions review the text before posting a proposal for incubation.. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump
[ https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615846#action_12615846 ] Ian Holsman commented on INCUBATOR-77: -- http://people.apache.org/~ianh/locallucene-ASF.tgz GPG sig: http://people.apache.org/~ianh/locallucene.tgz.sig $ md5 locallucene-ASF.tgz MD5 (locallucene-ASF.tgz) = 0eaf4dfab591e8fba997d10916049e81 headers for 99% were converted to standard ASL header. 1 file was not modified LonLatTrig.java in com.traversetechnologies.fulcrum.math as it is LGPL my understanding is that this code is being replaced with the code in the mqspatialbase directory, so will not be there in the medium term. [IP-GRANT] Local Lucene/Solr Code Dump -- Key: INCUBATOR-77 URL: https://issues.apache.org/jira/browse/INCUBATOR-77 Project: Incubator Issue Type: New Feature Environment: lucene.apache.org Reporter: Ian Holsman Attachments: locallucene.tgz.asc $ rpm -qf $(which md5sum) coreutils-5.97-12.1.el5 $ md5sum locallucene.tgz e470f7dfd963994eebb6c5002f810549 locallucene.tgz -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
I'll update the project proposal with names as soon as I get the chance. As explained in the proposal, we plan to move the project to a central location. Some of the internal project info/documentation (email, etc) is scattered around. The main focus/goal has been completing the core functionality of the pattern oriented framework. Regards, Ed --- On Tue, 7/22/08, Roland Weber [EMAIL PROTECTED] wrote: From: Roland Weber [EMAIL PROTECTED] Subject: Re: Jt Pattern Oriented Framework (looking for champion/mentors) To: general@incubator.apache.org Date: Tuesday, July 22, 2008, 4:22 AM David S (or rather Ed) wrote: Community One of the next objectives is to continue growing an active community of users and contributors. It is expected that community will continue to grow. So you already have an active community of users and contributors? Any public record of that? Names and/or numbers?
