aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Farrell <jfarr...@apache.org>
Subject Re: Incubator PMC/Board report for Jul 2014 ([ppmc])
Date Wed, 25 Jun 2014 18:12:20 GMT
Draft report below, If no changes are needed i'll post it. Would like to
continue for us to work on rc1 and be able to switch report to contain our
release candidate is under vote

-Jake




Aurora

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

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

  1. First release, progress being tracked in ticket AURORA-147
  2. Establish a consistent development process and release rhythm.
  3. Expanding the community and continuing to add new committers.

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

  - None at this time.

How has the community developed since the last report?

  Latest Additions:

  * PMC addition:           Mark Chu-Carroll, 2014-02-03
  * Contributor addition:   Mark Chu-Carroll, 2014-01-14

  Issue backlog status since last report:

  * Created:     257
  * Resolved:  161

  Mailing list activity since last report:

  * @dev        254 messages
  * issues       987 messages
  * @reviews  1487 messages

How has the project developed since the last report?

  - IRC weekly meetings, digest sent to dev@ list
  - Automating release workflows
  - Fixing issues brought up in our first release candidate

Date of last release:

  - No releases as of yet. We have created our first release candidate,
    0.5.0-rc0, and working to fix issues found within it. 0.5.0-rc1
    being targeted within the next week


Signed-off-by:

  [ ](aurora) Jake Farrell
  [ ](aurora) Benjamin Hindman
  [ ](aurora) Chris Mattmann
  [ ](aurora) Henry Saputra




On Wed, Jun 25, 2014 at 1:27 PM, Henry Saputra <henry.saputra@gmail.com>
wrote:

> Any volunteer to write up report for July?
>
> - Henry
>
> On Wed, Jun 25, 2014 at 7:15 AM, Marvin <no-reply@apache.org> wrote:
> >
> >
> > 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 July 2014, 10:30:30:00 PST.
> 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, Jul 2nd).
> >
> > 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.
> >
> > 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.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> >   http://wiki.apache.org/incubator/July2014
> >
> > Note: This 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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message