Podling Report Reminder - May 2018
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 May 2018, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, May 02). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/May2018 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] [Commented] (S2GRAPH-211) Include 's2jobs' test in CI
[ https://issues.apache.org/jira/browse/S2GRAPH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456058#comment-16456058 ] ASF GitHub Bot commented on S2GRAPH-211: GitHub user daewon opened a pull request: https://github.com/apache/incubator-s2graph/pull/163 [S2GRAPH-211] Include 's2jobs' test in CI Fixed the change of 'database meta' file and releasing hbase/s2graph related resource so that 's2jobs test' can be executed independently of 'whole s2graph project test'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/daewon/incubator-s2graph S2GRAPH-211 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-s2graph/pull/163.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #163 commit 204efabafcf25411f89cacbd5817f0dc8097b2e3 Author: daewonDate: 2018-04-26T08:50:17Z fix broken test commit 501716c8d793590f0205e84445273b3ef7420c74 Author: daewon Date: 2018-04-27T07:29:58Z Merge branch 'master' into S2GRAPH-211 * master: [S2GRAPH-210]: Rename package `mysqls` to `schema` update SafeUpdateCache constructor. fix compile error while test:compile. - rename mysqls package to schema. - remove GlobalIndex. - add toBytes, fromBytes on Schema. > Include 's2jobs' test in CI > --- > > Key: S2GRAPH-211 > URL: https://issues.apache.org/jira/browse/S2GRAPH-211 > Project: S2Graph > Issue Type: Improvement > Components: s2jobs >Reporter: Daewon Jeong >Assignee: Daewon Jeong >Priority: Minor > > Add s2jobs to the S2Graph CI and modify the s2jobs test so that it is not > affected by the entire s2graph project test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (S2GRAPH-211) Include 's2jobs' test in CI
Daewon Jeong created S2GRAPH-211: Summary: Include 's2jobs' test in CI Key: S2GRAPH-211 URL: https://issues.apache.org/jira/browse/S2GRAPH-211 Project: S2Graph Issue Type: Improvement Components: s2jobs Reporter: Daewon Jeong Assignee: Daewon Jeong Add s2jobs to the S2Graph CI and modify the s2jobs test so that it is not affected by the entire s2graph project test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)