Re: Oversight of non-mailinglist-ful podlings
Greg Stein wrote on Wed, Jan 04, 2012 at 20:03:40 -0500: > On Jan 4, 2012 7:50 PM, "Daniel Shahaf" wrote: > > Greg Stein wrote on Wed, Jan 04, 2012 at 14:45:24 -0500: > > > Couldn't we just have a default rule for asf/incubator/ go to > > > private@incubator? Once a podling is constructed and configured, > > > > You're glossing over some details here. How does the commit mail for > > "svn mkdir -mm ^/incubator/thismaybeapodlingname/" know what list to > > deliver itself to? > > > > The post-commit hook, the mailing lists, and the MX's, run each on > > a different host. > > Wouldn't it be something like: > > for_path = /incubator/podling/.* > send_to = podling-commits@... > > for_path = /incubator/* > send_to = private@incubator > > ... > > Of course, now I realize the config above would send two emails. There > isn't a marker that says "if nothing else matched" > There is suppress_if_match = true that can be used on the second rule. But with this design, each podling would have to be added individually. The current config does a pattern match and assumes that podling-commits@ exists if the commit contains /incubator/podlings/. > Hrm... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Oversight of non-mailinglist-ful podlings
FWIW I was under the impression is that infra@ is the default list for svnmailer when no other rule matches. - Original Message - > From: Greg Stein > To: Daniel Shahaf > Cc: general@incubator.apache.org > Sent: Wednesday, January 4, 2012 8:03 PM > Subject: Re: Oversight of non-mailinglist-ful podlings > > On Jan 4, 2012 7:50 PM, "Daniel Shahaf" > wrote: >> >> Greg Stein wrote on Wed, Jan 04, 2012 at 14:45:24 -0500: >> > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf > > wrote: >> > > Someone created >> > > > https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 >> > > before the devicemap-commits@ list was created. I expect no list >> > > received a commit mail about it. >> > > >> > > This PMC may want to review its mailer config and/or podling > creation >> > > policies to ensure that no changes slip unnoticed. Saying > "once the >> > > commits mail flow, check the svn tree to see what it contained > prior > to >> > > the first commit that was emailed about" might suffice. >> > >> > Couldn't we just have a default rule for asf/incubator/ go to >> > private@incubator? Once a podling is constructed and configured, >> >> You're glossing over some details here. How does the commit mail for >> "svn mkdir -mm ^/incubator/thismaybeapodlingname/" know what list > to >> deliver itself to? >> >> The post-commit hook, the mailing lists, and the MX's, run each on >> a different host. > > Wouldn't it be something like: > > for_path = /incubator/podling/.* > send_to = podling-commits@... > > for_path = /incubator/* > send_to = private@incubator > > ... > > Of course, now I realize the config above would send two emails. There > isn't a marker that says "if nothing else matched" > > Hrm... > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Oversight of non-mailinglist-ful podlings
On Jan 4, 2012 7:50 PM, "Daniel Shahaf" wrote: > > Greg Stein wrote on Wed, Jan 04, 2012 at 14:45:24 -0500: > > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf wrote: > > > Someone created > > > https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 > > > before the devicemap-commits@ list was created. I expect no list > > > received a commit mail about it. > > > > > > This PMC may want to review its mailer config and/or podling creation > > > policies to ensure that no changes slip unnoticed. Saying "once the > > > commits mail flow, check the svn tree to see what it contained prior to > > > the first commit that was emailed about" might suffice. > > > > Couldn't we just have a default rule for asf/incubator/ go to > > private@incubator? Once a podling is constructed and configured, > > You're glossing over some details here. How does the commit mail for > "svn mkdir -mm ^/incubator/thismaybeapodlingname/" know what list to > deliver itself to? > > The post-commit hook, the mailing lists, and the MX's, run each on > a different host. Wouldn't it be something like: for_path = /incubator/podling/.* send_to = podling-commits@... for_path = /incubator/* send_to = private@incubator ... Of course, now I realize the config above would send two emails. There isn't a marker that says "if nothing else matched" Hrm...
Re: Oversight of non-mailinglist-ful podlings
Greg Stein wrote on Wed, Jan 04, 2012 at 14:45:24 -0500: > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf wrote: > > Someone created > > https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 > > before the devicemap-commits@ list was created. I expect no list > > received a commit mail about it. > > > > This PMC may want to review its mailer config and/or podling creation > > policies to ensure that no changes slip unnoticed. Saying "once the > > commits mail flow, check the svn tree to see what it contained prior to > > the first commit that was emailed about" might suffice. > > Couldn't we just have a default rule for asf/incubator/ go to > private@incubator? Once a podling is constructed and configured, You're glossing over some details here. How does the commit mail for "svn mkdir -mm ^/incubator/thismaybeapodlingname/" know what list to deliver itself to? The post-commit hook, the mailing lists, and the MX's, run each on a different host. > then its commit emails would go to the correct place. > > Cheers, > -g > > - > 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: Oversight of non-mailinglist-ful podlings
Greg Stein wrote on Wed, Jan 04, 2012 at 18:51:59 -0500: > I worry that something not configured to go somewhere specific, might be > private. The mailer config stanza can/should use a 'for_repos = .*asf' directive to prevent this. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Oversight of non-mailinglist-ful podlings
Bertrand Delacretaz wrote on Wed, Jan 04, 2012 at 22:59:36 +0100: > On Wed, Jan 4, 2012 at 8:33 PM, Daniel Shahaf wrote: > > This PMC may want to review its mailer config and/or podling creation > > policies to ensure that no changes slip unnoticed. Saying "once the > > commits mail flow, check the svn tree to see what it contained prior to > > the first commit that was emailed about" might suffice. > > Sounds good to me. Committed r1227410 to staging (but not published yet). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Oversight of non-mailinglist-ful podlings
Greg Stein wrote on Wed, Jan 04, 2012 at 14:45:24 -0500: > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf wrote: > > Someone created > > https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 > > before the devicemap-commits@ list was created. I expect no list > > received a commit mail about it. > > > > This PMC may want to review its mailer config and/or podling creation > > policies to ensure that no changes slip unnoticed. Saying "once the > > commits mail flow, check the svn tree to see what it contained prior to > > the first commit that was emailed about" might suffice. > > Couldn't we just have a default rule for asf/incubator/ go to > private@incubator? Once a podling is constructed and configured, then > its commit emails would go to the correct place. We _could_, but someone would need to implement it. And infra has more than enough manual steps, thankyouverymuch. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Oversight of non-mailinglist-ful podlings
On Jan 4, 2012 4:01 PM, "sebb" wrote: > > On 4 January 2012 19:45, Greg Stein wrote: > > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf wrote: > >> Someone created > >> https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 > >> before the devicemap-commits@ list was created. I expect no list > >> received a commit mail about it. > >> > >> This PMC may want to review its mailer config and/or podling creation > >> policies to ensure that no changes slip unnoticed. Saying "once the > >> commits mail flow, check the svn tree to see what it contained prior to > >> the first commit that was emailed about" might suffice. > > > > Couldn't we just have a default rule for asf/incubator/ go to > > private@incubator? Once a podling is constructed and configured, then > > its commit emails would go to the correct place. > > Seems like a good idea, but why use private@ - commit mails are not > normally private are they? > > Would it not be better to send them to public-commits@incubator.apache.orgor > general@incubator? I worry that something not configured to go somewhere specific, might be private. Since this kind of misconfig should be rare, it shouldn't flood private@. It also puts them in front of the PMC itself, many who I hypothesize are *not* subscribed to general@ or public-commits@ (I never even heard of the latter!) Cheers, -g
Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC2
+1 Tommaso 2012/1/4 Karl Wright > Hello Incubator IPMC, > > Please vote on whether or not to release ManifoldCF 0.4-incubating, > RC2. This RC has passed our podling vote and awaits your inspection. > You can find the artifact at > http://people.apache.org/~kwright/apache-manifoldcf-0.4-incubating, or > in svn at > https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.4-incubating-RC2 > . > Thanks in advance! > > Karl >
Re: Oversight of non-mailinglist-ful podlings
On Wed, Jan 4, 2012 at 8:33 PM, Daniel Shahaf wrote: > Someone created > https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 > before the devicemap-commits@ list was created. I expect no list > received a commit mail about it. That's me, trying to move forward in the podling creation by doing what I can myself. > > This PMC may want to review its mailer config and/or podling creation > policies to ensure that no changes slip unnoticed. Saying "once the > commits mail flow, check the svn tree to see what it contained prior to > the first commit that was emailed about" might suffice. Sounds good to me. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release apache-manifoldcf-solr-3.x-plugin 0.1-incubating
+1 Tommaso 2011/12/29 Karl Wright > Sorry - you can find the proposed release package at: > http://people.apache.org/~kwright. > > On Thu, Dec 29, 2011 at 1:08 PM, Karl Wright wrote: > > Hello incubator, > > > > We've decided to release some of the ManifoldCF server or target > > system plugins with their own versioning and release schedule. Here's > > the third one. Please vote +1 if you agree it should be released. > > We've got one vote already (from Jukka, one of our mentors). > > > > Karl > > > > > > -- Forwarded message -- > > From: Jukka Zitting > > Date: Thu, Dec 15, 2011 at 12:35 PM > > Subject: Re: [RESULT][VOTE] Release apache-manifoldcf-solr-3.x-plugin > > 0.1-incubating > > To: connectors-...@incubator.apache.org > > > > > > Hi, > > > > +1 from me too (binding also for the upcoming IPMC vote) > > > > I checked the apache-manifoldcf-solr-3.x-plugin-0.1-incubating-src.tar.gz > > package with SHA1 checksum 14adbae8c05dc589a707208a172901cddd5c19d5. > > > > Some comments, none blocking: > > > > * The release signing guide [1] recommends to have also SHA1 checksums > > for the release. > > * The approach to do an svn checkout as a part of the build is a bit > > troublesome. The build will fail as soon as Lucene rearranges their > > svn tree. > > * Would it make sense to contribute this code directly to Solr instead > > of having it in ManifoldCF? Especially since the code has no direct > > ManifoldCF dependencies. > > > > [1] http://www.apache.org/dev/release-signing.html > > > > BR, > > > > Jukka Zitting > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release apache-manifoldcf-solr-4.x-plugin 0.1-incubating
+1 Tommaso 2011/12/29 Karl Wright > Sorry - you can find the proposed release package at: > http://people.apache.org/~kwright. > > On Thu, Dec 29, 2011 at 1:07 PM, Karl Wright wrote: > > Hello incubator, > > > > We've decided to release some of the ManifoldCF server or target > > system plugins with their own versioning and release schedule. Here's > > the second one. Please vote +1 if you agree it should be released. > > We've got one vote already (from Jukka, one of our mentors). > > > > Karl > > > > > > -- Forwarded message -- > > From: Jukka Zitting > > Date: Thu, Dec 15, 2011 at 12:40 PM > > Subject: Re: [RESULT][VOTE] Release apache-manifoldcf-solr-4.x-plugin > > 0.1-incubating > > To: connectors-...@incubator.apache.org > > > > > > Hi, > > +1 from me too (binding also for the upcoming IPMC vote) > > I checked the apache-manifoldcf-solr-4.x-plugin-0.1-incubating-src.tar.gz > > package with SHA1 checksum 84065fe25707beec3b25831a9df56579ad685a50. > > See my comments for the Solr 3.x plugin. > > > > BR, > > Jukka Zitting > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release apache-manifoldcf-sharepoint-3.0-plugin 0.1-incubating
+1 Tommaso 2011/12/29 Karl Wright > Hello incubator, > > We've decided to release some of the ManifoldCF server or target > system plugins with their own versioning and release schedule. Here's > the first one. Please vote +1 if you agree it should be released. > We've got one vote already (from Jukka, one of our mentors). > > Karl > > > -- Forwarded message -- > From: Jukka Zitting > Date: Thu, Dec 15, 2011 at 1:15 PM > Subject: Re: [RESULT][VOTE] Release > apache-manifoldcf-sharepoint-3.0-plugin 0.1-incubating > To: connectors-...@incubator.apache.org > > > Hi, > > +1 from me too (binding also for the upcoming IPMC vote) > > I checked the > apache-manifoldcf-sharepoint-3.0-plugin-0.1-incubating-src.tar.gz > package with SHA1 checksum 4400b19cf0940bae30778e9fdcb992122ecbc142. > Without Windows or SharePoint readily at hand I couldn't build the > package, just statically review it. > > One comment (not blocking) that applies also to the other components > is that since these components (AFAIUI) don't contain or use any > crypto code, we should remove the "Cryptographic Software Notice" > entries from the README files. Those notices should only be included > in components referenced in http://www.apache.org/licenses/exports/. > > BR, > > Jukka Zitting > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Oversight of non-mailinglist-ful podlings
On 4 January 2012 19:45, Greg Stein wrote: > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf wrote: >> Someone created >> https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 >> before the devicemap-commits@ list was created. I expect no list >> received a commit mail about it. >> >> This PMC may want to review its mailer config and/or podling creation >> policies to ensure that no changes slip unnoticed. Saying "once the >> commits mail flow, check the svn tree to see what it contained prior to >> the first commit that was emailed about" might suffice. > > Couldn't we just have a default rule for asf/incubator/ go to > private@incubator? Once a podling is constructed and configured, then > its commit emails would go to the correct place. Seems like a good idea, but why use private@ - commit mails are not normally private are they? Would it not be better to send them to public-comm...@incubator.apache.org or general@incubator? > Cheers, > -g > > - > 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] Chukwa 0.5.0 release candidate 0
On Wed, Jan 4, 2012 at 5:55 AM, sebb wrote: > The NOTCE and LICENSE files contain several strange characters, which > don't render OK. I will correct the UTF8 characters into plain ASCII text in rc1. > The NOTICE file also seems to contain references which are not required, e.g. > The Prototype AJAX library license does not seem to require a notice. > > The NOTICE file is for *required* notices only. From: https://issues.apache.org/jira/browse/LEGAL-59, it looks like BSD license do not require additional notice in the NOTICE file. How about MIT license? regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release apache-manifoldcf-0.4-incubating, RC2
Hello Incubator IPMC, Please vote on whether or not to release ManifoldCF 0.4-incubating, RC2. This RC has passed our podling vote and awaits your inspection. You can find the artifact at http://people.apache.org/~kwright/apache-manifoldcf-0.4-incubating, or in svn at https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.4-incubating-RC2. Thanks in advance! Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Oversight of non-mailinglist-ful podlings
On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf wrote: > Someone created > https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 > before the devicemap-commits@ list was created. I expect no list > received a commit mail about it. > > This PMC may want to review its mailer config and/or podling creation > policies to ensure that no changes slip unnoticed. Saying "once the > commits mail flow, check the svn tree to see what it contained prior to > the first commit that was emailed about" might suffice. Couldn't we just have a default rule for asf/incubator/ go to private@incubator? Once a podling is constructed and configured, then its commit emails would go to the correct place. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Oversight of non-mailinglist-ful podlings
Someone created https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271 before the devicemap-commits@ list was created. I expect no list received a commit mail about it. This PMC may want to review its mailer config and/or podling creation policies to ensure that no changes slip unnoticed. Saying "once the commits mail flow, check the svn tree to see what it contained prior to the first commit that was emailed about" might suffice. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Chukwa 0.5.0 release candidate 0
On 3 January 2012 18:41, Eric Yang wrote: > Dear IPMC members, > > Chukwa 0.5.0 is ready for release. > > The artifacts are available at: > > http://people.apache.org/~eyang/chukwa-0.5.0-rc0/ > > Documents are available at: > > http://people.apache.org/~eyang/chukwa-0.5.0-docs/ > > The SVN tag to be voted upon: > > https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc0/ The NOTCE and LICENSE files contain several strange characters, which don't render OK. The NOTICE file also seems to contain references which are not required, e.g. The Prototype AJAX library license does not seem to require a notice. The NOTICE file is for *required* notices only. > Chukwa's KEYS file containing PGP keys we use to sign the release: > > http://people.apache.org/~eyang/chukwa-0.5.0-rc0/KEYS > > Please download, evaluate, and vote on general@incubator. > > The same artifacts have been tested and voted on chukwa-dev mailing list. > > The PPMC vote thread is: > > http://www.mail-archive.com/chukwa-dev@incubator.apache.org/msg00814.html > > The vote will close at 12:30pm PST on Wednesday January 11, 2012. > > Thanks > > regards, > Eric > > - > 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: [DISCUSS] Apache Bean Validation as a TLP
I am OK with that, but lets give a last chance for any last comments or reviews from other IPMC members, I know this looks like *strictly* following the rules, but IMHO there is no harm in that :). On Tue, Jan 3, 2012 at 7:08 PM, Mark Struberg wrote: > +1 > > imo we can easily just start calling the VOTE. BVAL and the resolution has > been on spot several times. > > So I'd say we just move the last resolution text to our Wiki and do an > internal review for fixing the last itches and scratches. > > Then we can formally call the VOTE and are done. > > > LieGrue, > strub > > > > - Original Message - > > From: Mohammad Nour El-Din > > To: general@incubator.apache.org > > Cc: bval-...@incubator.apache.org > > Sent: Tuesday, January 3, 2012 4:17 PM > > Subject: [DISCUSS] Apache Bean Validation as a TLP > > > > Hi... > > > >It has been discussed, since a while, about the graduation of Apache > > Bean Validation, whether to graduate to a TLP or Subproject and whether > it > > is time or not, [1], [2] and [3]. > > In the past few weeks there has been a [VOTE], [4], which formally > > discussed the graduation to a TLP project. Result announcement can be > found > > here, [5]. The resolution charter content has been discussed and reviewed > > here [6]. > > > > The Apache Bean Validation community sees it is time to request an IPMC > > [VOTE] on recommending this resolution [7] to the ASF board. > > > > Accordingly, would you please cast your vote: > > > > [ ] +1 to recommend Bean Validation's graduation > > [ ] 0 don't care > > [ ] -1 no, don't recommend yet, (because...) > > > > The vote will be open for 72 hours. > > > > [1] - http://s.apache.org/oTC > > [2] - http://s.apache.org/I8C > > [3] - http://s.apache.org/EQE > > [4] - http://s.apache.org/rU > > [5] - http://s.apache.org/7Sw > > [6] - http://s.apache.org/S5F > > [7] - see below: > > > > ## Resolution to create a TLP from graduating Incubator podling > > > > X. Establish the Apache Bean Validation Project > > > >WHEREAS, the Board of Directors deems it to be in the best > >interests of the Foundation and consistent with the > >Foundation's purpose to establish a Project Management > >Committee charged with the creation and maintenance of > >open-source software related to creating an implementation > >compliant with JSR-303 and a library of pre-developed validators > >and extensions for distribution at no charge to the public. > > > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management > >Committee (PMC), to be known as the "Apache Bean Validation > > Project", > >be and hereby is established pursuant to Bylaws of the > >Foundation; and be it further > > > >RESOLVED, that the Apache Bean Validation Project be and hereby is > >responsible for the creation and maintenance of software > >related to creating an implementation compliant with JSR-303 > >and a library of pre-developed validators and extensions; and be > it > > further > > > >RESOLVED, that the office of "Vice President, Apache Bean > > Validation" be > >and hereby is created, the person holding such office to > >serve at the direction of the Board of Directors as the chair > >of the Apache Bean Validation Project, and to have primary > > responsibility > >for management of the projects within the scope of > >responsibility of the Apache Bean Validation Project; and be it > > further > > > >RESOLVED, that the persons listed immediately below be and > >hereby are appointed to serve as the initial members of the > >Apache Bean Validation Project: > > > > * Albert Lee > > * Carlos Vara Callau > > * David Jencks > > * Donald Woods > > * Gerhard Petracek > > * Jeremy Bauer > > * Kevan Lee Miller > > * Luciano Resende > > * Matthias Wessendorf > > * Matthew Jason Benson > > * Mohammad Nour El-Din > > * Niall Pemberton > > * Roman Stumm > > * Simone Tripodi > > * Mark Struberg > > > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Jason Benson > >be appointed to the office of Vice President, Apache Bean > > Validation, to > >serve in accordance with and subject to the direction of the > >Board of Directors and the Bylaws of the Foundation until > >death, resignation, retirement, removal or disqualification, > >or until a successor is appointed; and be it further > > > >RESOLVED, that the initial Apache Bean Validation PMC be and > hereby > > is > >tasked with the creation of a set of bylaws intended to > >encourage open development and increased participation in the > >Apache Bean Validation Project; and be it further > > > >RESOLVED, that the Apache Be
[VOTE] Chukwa 0.5.0 release candidate 0
Dear IPMC members, Chukwa 0.5.0 is ready for release. The artifacts are available at: http://people.apache.org/~eyang/chukwa-0.5.0-rc0/ Documents are available at: http://people.apache.org/~eyang/chukwa-0.5.0-docs/ The SVN tag to be voted upon: https://svn.apache.org/repos/asf/incubator/chukwa/tags/chukwa-0.5.0-rc0/ Chukwa's KEYS file containing PGP keys we use to sign the release: http://people.apache.org/~eyang/chukwa-0.5.0-rc0/KEYS Please download, evaluate, and vote on general@incubator. The same artifacts have been tested and voted on chukwa-dev mailing list. The PPMC vote thread is: http://www.mail-archive.com/chukwa-dev@incubator.apache.org/msg00814.html The vote will close at 12:30pm PST on Wednesday January 11, 2012. Thanks regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Bean Validation as a TLP
+1 Am 03.01.12 16:17, schrieb Mohammad Nour El-Din: Hi... It has been discussed, since a while, about the graduation of Apache Bean Validation, whether to graduate to a TLP or Subproject and whether it is time or not, [1], [2] and [3]. In the past few weeks there has been a [VOTE], [4], which formally discussed the graduation to a TLP project. Result announcement can be found here, [5]. The resolution charter content has been discussed and reviewed here [6]. The Apache Bean Validation community sees it is time to request an IPMC [VOTE] on recommending this resolution [7] to the ASF board. Accordingly, would you please cast your vote: [x] +1 to recommend Bean Validation's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, (because...) The vote will be open for 72 hours. [1] - http://s.apache.org/oTC [2] - http://s.apache.org/I8C [3] - http://s.apache.org/EQE [4] - http://s.apache.org/rU [5] - http://s.apache.org/7Sw [6] - http://s.apache.org/S5F [7] - see below: ## Resolution to create a TLP from graduating Incubator podling X. Establish the Apache Bean Validation Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to creating an implementation compliant with JSR-303 and a library of pre-developed validators and extensions for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Bean Validation Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Bean Validation Project be and hereby is responsible for the creation and maintenance of software related to creating an implementation compliant with JSR-303 and a library of pre-developed validators and extensions; and be it further RESOLVED, that the office of "Vice President, Apache Bean Validation" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Bean Validation Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Bean Validation Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Bean Validation Project: * Albert Lee * Carlos Vara Callau * David Jencks * Donald Woods * Gerhard Petracek * Jeremy Bauer * Kevan Lee Miller * Luciano Resende * Matthias Wessendorf * Matthew Jason Benson * Mohammad Nour El-Din * Niall Pemberton * Roman Stumm * Simone Tripodi * Mark Struberg NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Jason Benson be appointed to the office of Vice President, Apache Bean Validation, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Bean Validation PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Bean Validation Project; and be it further RESOLVED, that the Apache Bean Validation Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Bean Validation podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Bean Validation podling encumbered upon the Apache Incubator Project are hereafter discharged. Looking forward to your feedback and reply :) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.5-incubating(RC7)
It's time to terminate this vote. Obviously, we didn't get enough count, although all of the 3 votes are +1... I suggest extend this vote to next Wednesday, Jan 11th for more feedback. 在 2011年12月28日 上午12:45，Devin Han 写道： > Hi all, > > Please vote on releasing the following candidate as Apache ODF Toolkit > (incubating) version 0.5. This will be the first incubator release for > ODF Toolkit in Apache. > > This release candidate fixes the pom.xml file inconsistant issue found in > RC6. Thanks Yegor! > > The candidate for the ODF Toolkit 0.5-incubating release is available at: > > http://people.apache.org/~devinhan/odftoolkit-release/odftoolkit-0.5-incubating-rc7/ > > The release candidate is a zip archive of the sources in: > > https://svn.apache.org/repos/asf/incubator/odf/tags/odftoolkit-0.5-incubating/ > > The SHA1 checksum of the zip archive is > 4e97a1a79291035d590b5578caf79478dc3f6de8. > The MD5 checksum of the zip archive is 8883f036ee34282077d3c175329f6257. > > Besides source code, binary packages and javadoc packages are also listed > in： > > http://people.apache.org/~devinhan/odftoolkit-release/odftoolkit-0.5-incubating-rc7/ > > All of the artifacts supply three package formats, tar.gz, tar.bz2 and zip. > > Keys: > http://www.apache.org/dist/incubator/odftoolkit/KEYS > > Please vote on releasing this package as Apache ODF Toolkit 0.5-incubating. > The vote is open for the next full week, until Tuesday, Jan 3rd, 2012, > 6pm, because of the New Year holiday and passes if a majority of at least 3 > +1 IPMC votes are cast. > >[ ] +1 Release this package as Apache ODF Toolkit 0.5-incubating >[ ] -1 Do not release this package because... > > > To learn more about Apache ODF Toolkit, please access: > http://incubator.apache.org/odftoolkit/. > @OOo-Dev, @POI-Dev, @Tika-Dev and @PDFBox-Dev, so sorry for the interrupt. > CC to you just wish to get your feedback, as your projects have more or > less interaction with ODFToolkit and we need more votes. > > > Thanks, > Devin > -- -Devin
