Re: Release Verification Checklist
On Fri, Dec 6, 2013 at 1:40 AM, Marvin Humphrey mar...@rectangular.comwrote: On Thu, Dec 5, 2013 at 8:38 AM, sebb seb...@gmail.com wrote: On 5 December 2013 10:37, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Dec 3, 2013 at 11:39 PM, Marvin Humphrey mar...@rectangular.com wrote: ... Second, I'm amused that the commits list item was quietly dropped, but new checklist items have been inserted regarding the dev and private lists... Pure oversight on my part, sorry...but what would we do if no reviewer follows the commit lists? I don't think that's a reason to kill a release. Oversight of the commit list is vital; that is how we ensure that SCM only contains material that is permitted. The source release is then checked against SCM to ensure we are only published vetted material. If there is no review of the commit list, then the whole system breaks down. I certainly agree that following the commits list is essential (and sought to emphasize as much in the post at the top of the thread). I'd barely even considered the possibility that *none* of the reviewers might be following the commits list. However, I think that Bertrand's provenance checklist item largely achieves what I'd been grasping for with the commits list item, and fits much better into the context of approving the release. If nobody's following the commits list, that's an issue with serious implications for the project, but it's not a direct release blocker. If provenance is unsettled, though, that clearly blocks the release. Personally, I wouldn't feel confident checking the provenance item if I wasn't watching the commits list. It's true that the person making the commit affirms that they have the right to their contribution, but still, I feel like you need to at least be aware of what contributions have gone into the product. Maybe there ought to be a note to such effect on the explanations page. But in any case, I'm OK with the commits list item disappearing, so long as the provenance item stays. As of revision 14 (removing the dev list and private list items) I'm now generally satisfied with the content of the checklist items and hope to move on to refining the workflow and surrounding documentation. All the stuff required to be checked when voting on a release should be documented in the ASF doc about releases. That its not in that doc suggests its not required. If someone thinks something is required then they should go get consensus around that with the wider ASF and get the ASF doc updated. Podling releases are not quite the same as TLP releases, thats why they have the DISCLAIMER and incubating naming. I think we should be making it easier for podlings to do releases, if its really necessary then make an audit of the last release a requirement of graduation. ...ant
Re: [VOTE] Phoenix for incubator project
On 12/05/2013 01:43 PM, Stack wrote: Discussion of the Phoenix proposal has settled since its original posting on November 7th. Feedback has been incorporated. Let us now move to a vote. Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because... The latest version of the proposal can be found here [1]. It is also posted below for your convenience. Let the vote run 72 hours. Thank you, St.Ack 1. https://wiki.apache.org/incubator/PhoenixProposal Abstract Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. Proposal Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. Background Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. Rationale As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. Initial Goals The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. Current Status Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. Meritocracy The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. Community Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many are employed at Salesforce.com, there is a representative cross sampling of other organizations including Intel, Hortonworks, and Cloudera. Alignment Our proposed Phoenix effort aligns closely with Apache HBase. The HBase project perimeter is denoted by a simple byte-array based Create, Read, Update, Delete and Scan APIs with no current plans to extend beyond this bounds. Phoenix complements this with a higher
RE: [VOTE] Phoenix for incubator project
+1 from me. Regards Ram -Original Message- From: Bruno Mahé [mailto:bm...@apache.org] Sent: Friday, December 06, 2013 3:30 PM To: general@incubator.apache.org Subject: Re: [VOTE] Phoenix for incubator project On 12/05/2013 01:43 PM, Stack wrote: Discussion of the Phoenix proposal has settled since its original posting on November 7th. Feedback has been incorporated. Let us now move to a vote. Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because... The latest version of the proposal can be found here [1]. It is also posted below for your convenience. Let the vote run 72 hours. Thank you, St.Ack 1. https://wiki.apache.org/incubator/PhoenixProposal Abstract Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. Proposal Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. Background Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. Rationale As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. Initial Goals The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. Current Status Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. Meritocracy The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. Community Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many are employed at Salesforce.com, there is a representative
S4 Podling - May need some help
Hi, I completed my shepherd review of S4 now that their board report is in place. Here's a copy: The board report reflects my sentiments as well. S4 seems to be in a bit of rut. I tried kicking off some conversations on the dev mailing list, no luck. It seems like there are at best five active participants, between the users list and dev list. Considering that there hasn't been a commit since last board report, it doesn't come off as a good sign for me. I think retirement may be an option to start exploring. It seems like through a combination of low dev activity and low user feedback S4 is having difficulty progressing. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
+1 On Thu, Dec 5, 2013 at 1:43 PM, Stack st...@duboce.net wrote: Discussion of the Phoenix proposal has settled since its original posting on November 7th. Feedback has been incorporated. Let us now move to a vote. Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because... The latest version of the proposal can be found here [1]. It is also posted below for your convenience. Let the vote run 72 hours. Thank you, St.Ack 1. https://wiki.apache.org/incubator/PhoenixProposal Abstract Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. Proposal Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. Background Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. Rationale As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. Initial Goals The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. Current Status Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. Meritocracy The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. Community Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many are employed at Salesforce.com, there is a representative cross sampling of other organizations including Intel, Hortonworks, and Cloudera. Alignment Our proposed Phoenix effort aligns closely with Apache HBase. The HBase project perimeter is denoted by a simple byte-array based Create, Read,
Re: Release Verification Checklist
On Thu, Dec 5, 2013 at 2:32 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Dec 4, 2013 at 1:31 AM, Marvin Humphrey mar...@rectangular.com wrote: http://svn.apache.org/repos/asf/incubator/public/trunk/votes/$PODLING/$RC ... Added to a new usage proposal section at https://wiki.apache.org/incubator/ReleaseChecklist - does that proposal work for you guys? I like it. It basically looks like sebb-in-a-box to me (or should be elastic sebb these days?) ;-) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
+1 (binding) On Fri, Dec 6, 2013 at 8:44 AM, Jonathan Hsieh j...@cloudera.com wrote: +1 On Thu, Dec 5, 2013 at 1:43 PM, Stack st...@duboce.net wrote: Discussion of the Phoenix proposal has settled since its original posting on November 7th. Feedback has been incorporated. Let us now move to a vote. Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because... The latest version of the proposal can be found here [1]. It is also posted below for your convenience. Let the vote run 72 hours. Thank you, St.Ack 1. https://wiki.apache.org/incubator/PhoenixProposal Abstract Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. Proposal Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. Background Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. Rationale As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. Initial Goals The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. Current Status Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. Meritocracy The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. Community Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many are employed at Salesforce.com, there is a representative cross sampling of other
Re: [VOTE] Phoenix for incubator project
On 05/12/13 22:43, Stack wrote: Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because... +1 (binding) good luck! -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: S4 Podling - May need some help
Any updates from the mentors? I remember there were some sparks shown to re-energize the community about few months ago like to have weekly chats - Henry On Fri, Dec 6, 2013 at 4:10 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, I completed my shepherd review of S4 now that their board report is in place. Here's a copy: The board report reflects my sentiments as well. S4 seems to be in a bit of rut. I tried kicking off some conversations on the dev mailing list, no luck. It seems like there are at best five active participants, between the users list and dev list. Considering that there hasn't been a commit since last board report, it doesn't come off as a good sign for me. I think retirement may be an option to start exploring. It seems like through a combination of low dev activity and low user feedback S4 is having difficulty progressing. - 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] Phoenix for incubator project
+1 - binding Regards, Alan On Dec 5, 2013, at 1:43 PM, Stack st...@duboce.net wrote: Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because...
Re: S4 Podling - May need some help
On Fri, Dec 6, 2013 at 1:37 PM, Henry Saputra henry.sapu...@gmail.com wrote: Any updates from the mentors? I reviewed/signedoff on the report. I've commented both in public and in private to the s4 folks that they should consider retirement as an option. I was/am waiting to see what the community decides. Patrick I remember there were some sparks shown to re-energize the community about few months ago like to have weekly chats - Henry On Fri, Dec 6, 2013 at 4:10 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, I completed my shepherd review of S4 now that their board report is in place. Here's a copy: The board report reflects my sentiments as well. S4 seems to be in a bit of rut. I tried kicking off some conversations on the dev mailing list, no luck. It seems like there are at best five active participants, between the users list and dev list. Considering that there hasn't been a commit since last board report, it doesn't come off as a good sign for me. I think retirement may be an option to start exploring. It seems like through a combination of low dev activity and low user feedback S4 is having difficulty progressing. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
Stack stack at duboce.net writes: Should Phoenix become an Apache incubator project? +1 (non-binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Apache Sirona 0.1-incubating
On Sun, Dec 1, 2013 at 4:37 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Sirona 0.1-incubating. Hi, I've been compiling the list of Incubator releases for the last report cycle and I noticed that Sirona 0.1-incubating is in the dist area, but I couldn't find a RESULT message on general@incubator. I discovered that a RESULT message had been sent, but only to dev@sirona.incubator: http://s.apache.org/GIA It looks I missed to read some changes in the incubator process rules So in fact now 3 PPMC are required (see http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager ) So we are ok and I will finish release process. Contrary to that message, there has not been any process change yet -- three IPMC votes are still required to release. The release candidate has 2 as far as I can see. Although the bits have already been uploaded, I suggest continuing the vote on general@incubator. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Sirona 0.1-incubating
Hi Marvin, I just wanted to clarify with you. What you're saying is that a podling must have three PPMC votes. Once that is done, they must then send the release to the incubator to vote. Once 3 IPMC's approve it, it's ready to go, right? John On Fri, Dec 6, 2013 at 6:00 PM, Marvin Humphrey mar...@rectangular.com wrote: On Sun, Dec 1, 2013 at 4:37 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Sirona 0.1-incubating. Hi, I've been compiling the list of Incubator releases for the last report cycle and I noticed that Sirona 0.1-incubating is in the dist area, but I couldn't find a RESULT message on general@incubator. I discovered that a RESULT message had been sent, but only to dev@sirona.incubator: http://s.apache.org/GIA It looks I missed to read some changes in the incubator process rules So in fact now 3 PPMC are required (see http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager ) So we are ok and I will finish release process. Contrary to that message, there has not been any process change yet -- three IPMC votes are still required to release. The release candidate has 2 as far as I can see. Although the bits have already been uploaded, I suggest continuing the vote on general@incubator. Marvin Humphrey - 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: S4 Podling - May need some help
Thanks Patrick. - Henry On Fri, Dec 6, 2013 at 1:41 PM, Patrick Hunt ph...@apache.org wrote: On Fri, Dec 6, 2013 at 1:37 PM, Henry Saputra henry.sapu...@gmail.com wrote: Any updates from the mentors? I reviewed/signedoff on the report. I've commented both in public and in private to the s4 folks that they should consider retirement as an option. I was/am waiting to see what the community decides. Patrick I remember there were some sparks shown to re-energize the community about few months ago like to have weekly chats - Henry On Fri, Dec 6, 2013 at 4:10 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, I completed my shepherd review of S4 now that their board report is in place. Here's a copy: The board report reflects my sentiments as well. S4 seems to be in a bit of rut. I tried kicking off some conversations on the dev mailing list, no luck. It seems like there are at best five active participants, between the users list and dev list. Considering that there hasn't been a commit since last board report, it doesn't come off as a good sign for me. I think retirement may be an option to start exploring. It seems like through a combination of low dev activity and low user feedback S4 is having difficulty progressing. - 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 - 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] Phoenix for incubator project
+1 (non-binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Sirona 0.1-incubating
On Fri, Dec 6, 2013 at 3:23 PM, John D. Ament john.d.am...@gmail.com wrote: I just wanted to clarify with you. What you're saying is that a podling must have three PPMC votes. Once that is done, they must then send the release to the incubator to vote. Once 3 IPMC's approve it, it's ready to go, right? Here's the official answer, from the Incubator's policy page: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Our release management guide, as is often the case, duplicates information better described elsewhere, adding inaccuracies and misleading rephrasings. http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
+1 //mujtaba chohan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org