[GitHub] incubator-predictionio pull request #417: [PIO-66] JIRA and release process ...

[shimamoto]

GitHub user shimamoto opened a pull request:

https://github.com/apache/incubator-predictionio/pull/417

[PIO-66] JIRA and release process for PredictionIO


https://issues.apache.org/jira/browse/PIO-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shimamoto/incubator-predictionio 
PIO-66_jira-processes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-predictionio/pull/417.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 #417


commit 4c2d65731a9bf11be28421c17be2fbd9cb707a33
Author: shimamoto 
Date:   2017-07-31T09:53:54Z

[PIO-66] Document JIRA processes and add to public documentation.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (PIO-66) Document JIRA processes and add to public documentation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIO-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108241#comment-16108241
 ] 

ASF GitHub Bot commented on PIO-66:
---

GitHub user shimamoto opened a pull request:

https://github.com/apache/incubator-predictionio/pull/417

[PIO-66] JIRA and release process for PredictionIO


https://issues.apache.org/jira/browse/PIO-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shimamoto/incubator-predictionio 
PIO-66_jira-processes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-predictionio/pull/417.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 #417


commit 4c2d65731a9bf11be28421c17be2fbd9cb707a33
Author: shimamoto 
Date:   2017-07-31T09:53:54Z

[PIO-66] Document JIRA processes and add to public documentation.




> Document JIRA processes and add to public documentation
> ---
>
> Key: PIO-66
> URL: https://issues.apache.org/jira/browse/PIO-66
> Project: PredictionIO
>  Issue Type: Task
>Reporter: Sara Asher
>Assignee: Sara Asher
>
> https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_X8Xz8HKkYO2QC12GD3ZKP9g/edit#heading=h.4og7ud94e5g1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

August 2017 Release

[Donald Szeto]

Hey all,

To adhere to the proposed release cadence by Sara, let's shoot to cut a
release in early August that addresses all the top level graduation issues.

How does the developer community feel about this? Any major issues that we
should also resolve with this release? It looks like many TLP cleanup, new
features and bug fixes have already gone into the current development
branch.

Regards,
Donald

August 2017 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. Mentors, if this is good to go, please
put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. Our new committers have been actively contributing new features and
bug fixes to the core codebase.
  2. There are new local meetups about PredictionIO in Japan.
  3. There has been growing integration effort of PredictionIO on the
Heroku platform.
  4. Increased traffic on the user mailing list.

How has the project developed since the last report?

  1. Around 40 pull requests have been accepted and merged since 0.11's
release, from both committers and contributors.
  2. On track to stick with a bi-monthly release schedule. Proposing a new
release for the beginning of August.
  3. Many cleanup effort into TLP graduation.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Mars Hall was elected as committer and PMC member on July 8, 2017.

[REMINDER] Policies around Publicity & Press

[John D. Ament]

All Podlings,

In recent days I've been contacted about several publicity issues that have
gone a bit off kilter.  I wanted to remind podlings two very import
policies.

1. Podlings MUST coordinate with the Public Relations Committee with all
publicity activities.
2. The Press Team MUST review any press releases or similar communication
referencing a podling before it is published.

Relevant Links:

https://incubator.apache.org/guides/branding.html#publicity_activities
https://incubator.apache.org/guides/branding.html#publicity_throughout_the_incubation_process

Please reach out with any concerns.

Regards,

John D. Ament
VP, Apache Incubator