Re: [VOTE] Apache Chemistry OpenCMIS 0.1.0-incubating (RC2)
I've had a look, and it all looks good. The licensing and legal doc in the artifacts looks fine, the sigs verify, src builds etc. +1 ...ant On Tue, Sep 14, 2010 at 1:02 PM, Gabriele Columbro gabri...@apache.org wrote: Dear Incubator PMC members, on behalf of the Chemistry dev team, I'd like to ask your approval to release the RC2 packages as Chemistry OpenCMIS 0.1.0-incubating. Legal and packaging issues - that blocked RC1- should have been now resolved (https://issues.apache.org/jira/browse/CMIS-224), while detailed release notes can be found in Jira at: https://issues.apache.org/jira/browse/CMIS/fixforversion/12315133. The release has passed the Chemistry incubator PMC vote: http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201009.mbox/%3cf6d8594e-4913-4af6-aaab-a1b30e951...@apache.org%3e. During the vote, also 2 IPMC (Nick Burch Jukka Zitting) votes have been collected, so we'd need one more IPMC +1 to proceed with the release. Main release candidate packages (for distribution at apache.org/dist) are at: http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-rc2/dist/ The full set of Maven artifacts (for distribution at repository.apache.org) is at: https://repository.apache.org/content/repositories/orgapachechemistry-012/ Sources tag can be found at: http://svn.apache.org/repos/asf/incubator/chemistry/opencmis/tags/chemistry-opencmis-0.1.0-incubating-RC2/ The staging maven documentation site is at : http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-rc2/site/ (full integration tests at: http://bit.ly/b07hK8) Artifacts have been signed using key D0383AE5 (publicly available at http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xB0E9DD9ED0383AE5 and under http://svn.apache.org/repos/asf/incubator/chemistry/opencmis/trunk/KEYS). The vote is open for 72 hours. Please cast your votes! [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks in advance! Gabriele -- Gabriele Columbro Alfresco Software, Ltd. http://www.mindthegab.com http://twitter.com/mindthegabz Keyboard not found. Press F1 to continue. - 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 Whirr version 0.1.0-incubating
Looks ok, +1. The binary jar whirr-cli-0.1.0-incubating.jar is missing the incubator DISCLAIMER file but that file is in the other artifacts like the src distro so i guess its enough to just fix that next time. Its also a bit hard to work out if all the licenses are included for all the stuff thats included in that jar as theres so much in it, it did have a few i check but it would be helpful to have something like the main LICENSE file or a README summarise whats there and the licensing. ...ant On Tue, Sep 14, 2010 at 7:19 PM, Tom White tomwh...@apache.org wrote: This is the first incubator release for Apache Whirr, version 0.1.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/201009.mbox/%3caanlktinio1np6d+gbnm4w6jjcg-6koe7x8begkuxr...@mail.gmail.com%3e The issues fixed for 0.1.0-incubating https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315111styleName=HtmlprojectId=1230 Source and binary files: http://people.apache.org/~tomwhite/whirr-releases/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-009 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.1.0-incubating 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] ALOIS to enter the incubator
Hi, On Fri, Sep 17, 2010 at 1:37 AM, Urs Lerch m...@ulerch.net wrote: ...since ALOIS should become a community project, I still think the followers of it should decide which communication channell they prefer. (By the way, I myself sure am no fan of chats.)... See also our comments in the Real-time communication thread on this list. The if it didn't happen on the dev list, it didn't happen rule is not negociable, although additional communications channels can of course be useful. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: gXML project moved to Google Code
Hi, On Fri, Sep 17, 2010 at 8:13 AM, Eric Johnson e...@tibco.com wrote: ...We intend to follow what we understand of the Apache way as best we can - including holding discussions publicly, voting on releases publicly, paying careful attention to licensing concerns, using tools that Apache folks are comfortable with (Maven), and generally making sure other people are comfortable with getting involved That's cool, and as you intend to come back here eventually, make sure you have agreements with your committers, that allow you to move their code back here when the time comes. Something like http://www.apache.org/licenses/icla.txt -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] ALOIS to enter the incubator
...since ALOIS should become a community project, I still think the followers of it should decide which communication channell they prefer. (By the way, I myself sure am no fan of chats.)... The if it didn't happen on the dev list, it didn't happen rule is not negociable, although additional communications channels can of course be useful. I am not a fan of chats and not even sending chat protocols to the dev list. Sending a completed chat protocol is just announcing the result of a discussion with only a few partners. Its very difficult to step up afterwards and of course difficult to read (imho). If I would be the ALOIS project, I would remove this chat from my wishlist and go with mailinglists only, what is the standard for all apache projects. Just my 2 cent cheers - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kitty to Enter the Incubator
On 15.09.2010 09:20, msacks wrote: At the advisement of the list, we have created a brand-new thread here for voting on the kitty proposal. The wiki page is located at: http://wiki.apache.org/incubator/KittyProposal +1 (non-binding) I'm interested in contributing also. Regards, Rainer - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kitty to Enter the Incubator
+1 (binding) On Sep 15, 2010, at 3:20 AM, msacks wrote: At the advisement of the list, we have created a brand-new thread here for voting on the kitty proposal. The wiki page is located at: http://wiki.apache.org/incubator/KittyProposal Thanks. - 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: Real-time communication (was [VOTE] ALOIS to enter the incubator)
I still don't see how that gets around the perception, and the reality, that development is being done outside the list. So I don't see that proposal as helping out at all... On Sep 16, 2010, at 3:27 PM, Scott Deboy wrote: I understand the concern raised by the use of real-time communication for Apache projects - that decisions may be made off-list, and that folks who aren't a party to the real-time communication do not have the opportunity to benefit from or impact the decisions that result from the real-time communication. The proposal does offer what seems to be a reasonable compromise: 'we would send the logs daily to the mailing list.' Daily chat logs posted to the dev list, coupled with good mentoring and guidance that decisions need to be made on the mailing list, would seem to minimize the risk. I'm interested in what others think of their proposal for supporting real-time communication, and curious what others are doing, if anything, to support the growing interest in real-time communication between project participants. Scott On Thu, Sep 16, 2010 at 10:49 AM, Craig L Russell craig.russ...@oracle.comwrote: Hi Urs, My only concern is the request to have a chat channel. There's wide use of chat channels in Apache (the periodic board and members' meetings make use of them, and infrastructure uses channels to advantage). But for an incubating project, I'd strongly discourage use of chat as a communication channel. +1 Craig On Aug 26, 2010, at 9:09 AM, Urs Lerch wrote: Hi, I would like to call a vote for accepting ALOIS for incubation in the Apache Incubator. The full proposal is available below and on the proposal wiki page (http://wiki.apache.org/incubator/AloisProposal). We ask the Incubator PMC to sponsor it, with Scott Deboy volunteering as Champion and Mentor. Additional mentors are warmly welcome. Please cast your vote: [ ] +1, bring ALOIS into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring ALOIS into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. Thanks, Urs = Preface = ALOIS is a log collection and correlation software with reporting and alarming functionalities. It has been implemented by the Swiss company IMSEC for a customer about five years ago. GPL-licenced, implemented in Ruby and completely based on other OSS-licensed components, it was designed for the open source community right from the start. Now that the software has shown its functioning over several years in production with the one customer and one IMSEC-internal installation, it seems to be the right time to open it to a wider community. = Abstract = ALOIS stands for „Advanced Logging and Intrusion Detection System“ and is meant to be a fully implemented open source SIEM (security information and event management) system. = Proposal = While almost all other SIEM software, be it closed or open source, concentrate on the technological part of security monitoring, ALOIS is aimed to monitor the security of the content. It intends to be pro-active in the detection of potential loss, theft, mistaken modification or unauthorized access. ALOIS works on log messages and thus contains all the basic functionality of a conventional SIEM, as centralized collecting, normalizing, aggregation, analyzing and correlating of all log messages, as well as reporting all security related events. Therefore it can be used as any other SIEM. ALOIS consists of five modules interacting to ensure a scaleable functionality of a SIEM: * Insink is the message sink, which is the receiving entry point for all the different log messages into ALOIS. It is partly based on the syslog-ng software. Insink listens for messages (UDP), waits for messages (TCP), receives message collections (files, emails) and pre-filters them to prevent from message flow overload. * Pumpy is the incoming FIFO buffer, implemented as a relational database tables. which contain the incoming original messages (in raw format). In a complex system setup, there may be several insink instances, e.g. for a group of hosts, for specific types of messages, or for high-avaliablity. * Prisma contains logic to split up the text of log messages into separate fields, based on regular expressions. Actually, prisma is a set of prismi, each one prisma for one type of log message (apache, cisco etc. Several prismi can be applied to the same message. This allows for stacked messages, i.e. forwarded log messages contained in compressed files contained in e-mail messages. The data retrieved form the log messages is stored in a database called Dobby. Due to prisma being written in Ruby, prismi can be applied interactively (when having system access). * Dobby is the central log database. It should be separated from the Pumpy
Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)
Hi To cut a long story short: ALOIS is _not_ about a chat channel, it's a tool for security incident and event management. Since the chat channell in the required resources list was only a wish, I gladly dropped it off the proposal. Best Urs Am Freitag, den 17.09.2010, 07:32 -0400 schrieb Jim Jagielski: I still don't see how that gets around the perception, and the reality, that development is being done outside the list. So I don't see that proposal as helping out at all... On Sep 16, 2010, at 3:27 PM, Scott Deboy wrote: I understand the concern raised by the use of real-time communication for Apache projects - that decisions may be made off-list, and that folks who aren't a party to the real-time communication do not have the opportunity to benefit from or impact the decisions that result from the real-time communication. The proposal does offer what seems to be a reasonable compromise: 'we would send the logs daily to the mailing list.' Daily chat logs posted to the dev list, coupled with good mentoring and guidance that decisions need to be made on the mailing list, would seem to minimize the risk. I'm interested in what others think of their proposal for supporting real-time communication, and curious what others are doing, if anything, to support the growing interest in real-time communication between project participants. Scott On Thu, Sep 16, 2010 at 10:49 AM, Craig L Russell craig.russ...@oracle.comwrote: Hi Urs, My only concern is the request to have a chat channel. There's wide use of chat channels in Apache (the periodic board and members' meetings make use of them, and infrastructure uses channels to advantage). But for an incubating project, I'd strongly discourage use of chat as a communication channel. +1 Craig On Aug 26, 2010, at 9:09 AM, Urs Lerch wrote: Hi, I would like to call a vote for accepting ALOIS for incubation in the Apache Incubator. The full proposal is available below and on the proposal wiki page (http://wiki.apache.org/incubator/AloisProposal). We ask the Incubator PMC to sponsor it, with Scott Deboy volunteering as Champion and Mentor. Additional mentors are warmly welcome. Please cast your vote: [ ] +1, bring ALOIS into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring ALOIS into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. Thanks, Urs = Preface = ALOIS is a log collection and correlation software with reporting and alarming functionalities. It has been implemented by the Swiss company IMSEC for a customer about five years ago. GPL-licenced, implemented in Ruby and completely based on other OSS-licensed components, it was designed for the open source community right from the start. Now that the software has shown its functioning over several years in production with the one customer and one IMSEC-internal installation, it seems to be the right time to open it to a wider community. = Abstract = ALOIS stands for „Advanced Logging and Intrusion Detection System“ and is meant to be a fully implemented open source SIEM (security information and event management) system. = Proposal = While almost all other SIEM software, be it closed or open source, concentrate on the technological part of security monitoring, ALOIS is aimed to monitor the security of the content. It intends to be pro-active in the detection of potential loss, theft, mistaken modification or unauthorized access. ALOIS works on log messages and thus contains all the basic functionality of a conventional SIEM, as centralized collecting, normalizing, aggregation, analyzing and correlating of all log messages, as well as reporting all security related events. Therefore it can be used as any other SIEM. ALOIS consists of five modules interacting to ensure a scaleable functionality of a SIEM: * Insink is the message sink, which is the receiving entry point for all the different log messages into ALOIS. It is partly based on the syslog-ng software. Insink listens for messages (UDP), waits for messages (TCP), receives message collections (files, emails) and pre-filters them to prevent from message flow overload. * Pumpy is the incoming FIFO buffer, implemented as a relational database tables. which contain the incoming original messages (in raw format). In a complex system setup, there may be several insink instances, e.g. for a group of hosts, for specific types of messages, or for high-avaliablity. * Prisma contains logic to split up the text of log messages into separate fields, based on regular expressions. Actually, prisma is a set of prismi, each one prisma for one type of log message (apache, cisco etc. Several prismi
Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)
On 9/17/2010 9:41 AM, Urs Lerch wrote: To cut a long story short: ALOIS is _not_ about a chat channel, it's a tool for security incident and event management. Since the chat channell in the required resources list was only a wish, I gladly dropped it off the proposal. Hi Urs, While I certainly don't think a chat channel needs to be on the proposal (for one thing, Apache projects tend to just use freenode's IRC network), I'd like to strongly reiterate Bertrand's points. Off-list conversation is going to happen any time you have multiple devs working at the same company, living in the same town, or attending the same ApacheCon. Real-time chats are often the source of very valuable insights, and having an online hang-out spot for a project has in the past been hugely worthwhile to the projects I've been involved with, both for devs and users. As long as no serious decisions are made without consulting the list, and someone posts summaries of all conversations that significantly affect the project, real-time channels are fine. The point is that someone looking back at the project from five years down the road should be able to really see what happened by looking at the archives -- not that real-time is a Bad Thing. Thanks, --Glen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)
+1. It's hypocrisy to tell podlings that chat is entirely intolerable when plenty of running projects have them. On Fri, Sep 17, 2010 at 9:58 AM, Glen Daniels g...@thoughtcraft.com wrote: On 9/17/2010 9:41 AM, Urs Lerch wrote: To cut a long story short: ALOIS is _not_ about a chat channel, it's a tool for security incident and event management. Since the chat channell in the required resources list was only a wish, I gladly dropped it off the proposal. Hi Urs, While I certainly don't think a chat channel needs to be on the proposal (for one thing, Apache projects tend to just use freenode's IRC network), I'd like to strongly reiterate Bertrand's points. Off-list conversation is going to happen any time you have multiple devs working at the same company, living in the same town, or attending the same ApacheCon. Real-time chats are often the source of very valuable insights, and having an online hang-out spot for a project has in the past been hugely worthwhile to the projects I've been involved with, both for devs and users. As long as no serious decisions are made without consulting the list, and someone posts summaries of all conversations that significantly affect the project, real-time channels are fine. The point is that someone looking back at the project from five years down the road should be able to really see what happened by looking at the archives -- not that real-time is a Bad Thing. Thanks, --Glen - 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: Real-time communication (was [VOTE] ALOIS to enter the incubator)
Hi Glen Thanks for your input and a different view. I took the chat channell off the proposal, because I don't want that the project to be assessed on this single point. If a chat is useful for the followers, why not, as long as it is transparent and decisions are not made that way. Best Urs Am Freitag, den 17.09.2010, 09:58 -0400 schrieb Glen Daniels: On 9/17/2010 9:41 AM, Urs Lerch wrote: To cut a long story short: ALOIS is _not_ about a chat channel, it's a tool for security incident and event management. Since the chat channell in the required resources list was only a wish, I gladly dropped it off the proposal. Hi Urs, While I certainly don't think a chat channel needs to be on the proposal (for one thing, Apache projects tend to just use freenode's IRC network), I'd like to strongly reiterate Bertrand's points. Off-list conversation is going to happen any time you have multiple devs working at the same company, living in the same town, or attending the same ApacheCon. Real-time chats are often the source of very valuable insights, and having an online hang-out spot for a project has in the past been hugely worthwhile to the projects I've been involved with, both for devs and users. As long as no serious decisions are made without consulting the list, and someone posts summaries of all conversations that significantly affect the project, real-time channels are fine. The point is that someone looking back at the project from five years down the road should be able to really see what happened by looking at the archives -- not that real-time is a Bad Thing. Thanks, --Glen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)
On 09/17/2010 08:20 AM, Benson Margulies wrote: +1. It's hypocrisy to tell podlings that chat is entirely intolerable when plenty of running projects have them. +1 indeed. If not, ATS is in big trouble :). We have a very active community in the IRC room, where we brainstorm and help each other out all the time. Of course, often times discussions are moved over into the dev@ (and users@) mailing lists, but in many cases, those email threads start off because of an initial discussion in the IRC room. To us, real-time communications (e.g. IRC), is invaluable. Maybe we're wrong (but I certainly hope not). -- leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)
On Fri, Sep 17, 2010 at 5:21 PM, Leif Hedstrom zw...@apache.org wrote: On 09/17/2010 08:20 AM, Benson Margulies wrote: +1. It's hypocrisy to tell podlings that chat is entirely intolerable when plenty of running projects have them. +1 indeed. If not, ATS is in big trouble :). We have a very active community in the IRC room, where we brainstorm and help each other out all the time I don't think anybody said chat is entirely intolerable - not me at least, see my earlier message in this thread. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)
On 9/17/2010 11:27 AM, Bertrand Delacretaz wrote: On Fri, Sep 17, 2010 at 5:21 PM, Leif Hedstrom zw...@apache.org wrote: +1 indeed. If not, ATS is in big trouble :). We have a very active community in the IRC room, where we brainstorm and help each other out all the time I don't think anybody said chat is entirely intolerable - not me at least, see my earlier message in this thread. Yup, that's why I referenced your message earlier - the only reason I continued the thread was to make sure that Urs got that there was a large chat is good when used wisely contingent to balance the chat is bad impression he might have gotten. That said, we can probably end this thread now. Unless anyone wants to take it to #apache-realtime, that is. :) --G - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kitty to Enter the Incubator
Raindrops, Senaca I will add you to the wiki page as contributors. Thanks for jumping in. It might be a while until I am able to get to a computer and put you on there. On Sep 17, 2010 3:31 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 15.09.2010 09:20, msacks wrote: At the advisement of the list, we have created a brand-new thread here for voting on the kitty proposal. The wiki page is located at: http://wiki.apache.org/incubator/KittyProposal +1 (non-binding) I'm interested in contributing also. Regards, Rainer
[VOTE][RESULT] Apache Chemistry OpenCMIS 0.1.0-incubating (RC2) PASSED
Hi all, after 72 hours (actually almost 77 now :) this vote has started and together with those received on the podling list [1], we have now received sufficient IPMC binding votes to proceed with the release of Chemistry OpenCMIS 0.1.0. Resuming, we got 3 binding IPMC +1 votes and no 0 or -1 votes as listed below: +1 Nick Burch +1 Jukka Zitting +1 Ant Elder I'll proceed with distribution [2] , announcement [3] and final cleanup [4]. I'd like to take the opportunity to thank everyone that helped making this 1st release happen, *especially* the dev team for delivering a great piece of software and the mentors / incubator at large for helping us growing Chemistry the ASF way. And let this be just the 0.1st of many successful releases :) Thanks, Gabriele [1] http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201009.mbox/%3cf6d8594e-4913-4af6-aaab-a1b30e951...@apache.org%3e [2] http://incubator.apache.org/guides/releasemanagement.html#understanding-distribution [3] http://incubator.apache.org/guides/releasemanagement.html#announcements [4] https://cwiki.apache.org/confluence/display/CMIS/OpenCMIS+Maven+Release+Documentation #OpenCMISMavenReleaseDocumentation-PostReleaseCleanup Begin forwarded message: On Tue, Sep 14, 2010 at 1:02 PM, Gabriele Columbro gabri...@apache.org wrote: Dear Incubator PMC members, on behalf of the Chemistry dev team, I'd like to ask your approval to release the RC2 packages as Chemistry OpenCMIS 0.1.0-incubating. Legal and packaging issues - that blocked RC1- should have been now resolved (https://issues.apache.org/jira/browse/CMIS-224), while detailed release notes can be found in Jira at: https://issues.apache.org/jira/browse/CMIS/fixforversion/12315133. The release has passed the Chemistry incubator PMC vote: http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201009.mbox/%3cf6d8594e-4913-4af6-aaab-a1b30e951...@apache.org%3e . During the vote, also 2 IPMC (Nick Burch Jukka Zitting) votes have been collected, so we'd need one more IPMC +1 to proceed with the release. Main release candidate packages (for distribution at apache.org/ dist) are at: http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-rc2/dist/ The full set of Maven artifacts (for distribution at repository.apache.org) is at: https://repository.apache.org/content/repositories/orgapachechemistry-012/ Sources tag can be found at: http://svn.apache.org/repos/asf/incubator/chemistry/opencmis/tags/chemistry-opencmis-0.1.0-incubating-RC2/ The staging maven documentation site is at : http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-rc2/site/ (full integration tests at: http://bit.ly/b07hK8) Artifacts have been signed using key D0383AE5 (publicly available at http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xB0E9DD9ED0383AE5 and under http://svn.apache.org/repos/asf/incubator/chemistry/opencmis/trunk/KEYS) . The vote is open for 72 hours. Please cast your votes! [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks in advance! Gabriele -- Gabriele Columbro Alfresco Software, Ltd. http://www.mindthegab.com http://twitter.com/mindthegabz Keyboard not found. Press F1 to continue. - 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 -- Gabriele Columbro Alfresco Software, Ltd. http://www.mindthegab.com http://twitter.com/mindthegabz Keyboard not found. Press F1 to continue. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Whirr version 0.1.0-incubating
+1 Checked that src tarball has a correct signature md5sum. Also ran RAT over the extracted sources and the licensing looks good. Doug On 09/14/2010 11:19 AM, Tom White wrote: This is the first incubator release for Apache Whirr, version 0.1.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/201009.mbox/%3caanlktinio1np6d+gbnm4w6jjcg-6koe7x8begkuxr...@mail.gmail.com%3e The issues fixed for 0.1.0-incubating https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315111styleName=HtmlprojectId=1230 Source and binary files: http://people.apache.org/~tomwhite/whirr-releases/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-009 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.1.0-incubating 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
