tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@apache.org>
Subject Re: [DISCUSS] Graduation
Date Thu, 19 Jun 2014 17:22:22 GMT
Thanks for starting this discussion, Chris!

Yes, the TEZ project is growing well, +1 for graduation!

+1 for starting with Hitesh.

We can also cleanup the committer/PMC list at the time of graduation to
reflect the latest reality.

+Vinod

On Mon, Jun 16, 2014 at 8:07 PM, Mattmann, Chris A (3980) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hey Guys,
>
> So at first I was thinking - what is ChrisD talking about - Tez hasn't
> really been active/etc., and why does he think the community is ready
> for graduation.
>
> Then I checked the mail archives:
>
> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev
>
> Jun 2014 68
> May 2014 62
> Apr 2014 49
> Mar 2014 59
> Feb 2014 82
> Jan 2014 52
> Dec 2013 35
> Nov 2013 59
> Oct 2013 51
>
> [X] Good mailing list activity, increasing from prior months
>
> Then I checked private and for additions of new people:
> https://mail-search.apache.org/members/private-arch/tez-private
> (IPMC and/or PPMC and/or ASF members only)
>
> Jun 2014 13
> May 2014 34
>
>
> [X] Over 7 new committers and PPMC members added (minor nit on bulk
> VOTE'ing, but no biggie).
>
> Looking for releases, I see 3 releases:
>
> https://dist.apache.org/repos/dist/release/incubator/tez/
>
>
> * tez-0.2.0-incubating/
> <
> https://dist.apache.org/repos/dist/release/incubator/tez/tez-0.2.0-incubat
> ing/
> <https://dist.apache.org/repos/dist/release/incubator/tez/tez-0.2.0-incubating/>
> >
> * tez-0.3.0-incubating/
> <
> https://dist.apache.org/repos/dist/release/incubator/tez/tez-0.3.0-incubat
> ing/
> <https://dist.apache.org/repos/dist/release/incubator/tez/tez-0.3.0-incubating/>
> >
> * tez-0.4.0-incubating/
> <
> https://dist.apache.org/repos/dist/release/incubator/tez/tez-0.4.0-incubat
> ing/
> <https://dist.apache.org/repos/dist/release/incubator/tez/tez-0.4.0-incubating/>
> >
>
> And here:
>
> https://archive.apache.org/dist/incubator/tez/
>
>
> I see 3 releases (should probably delete everything in dist.apache.org but
> 0.4.0-incubating.
>
> [X] Made releases, > 1 in the incubator.
>
> Looking at the mailing list traffic, there is also good discussion and
> answering of
> user questions, etc. I think the project *IS* ready to graduate. My bad!
>
> At least I made up for it by making a convincing case for you guys to
> graduate ;)
> Great job guys.
>
> Next steps are:
>
> 1. Decide who will be VP (Hitesh?)
> 2. Draft up graduation resolution (search mail-archives for old ones, grab
> the
> one e.g., that I used for Spark and adapt it)
> 3. Wait 48-72 hours on this DISCUSS thread and see if people think we're
> ready.
> 4. Once 48-72 hours done and #2 done, and #1 done, [VOTE] thread on
> dev@tez.i.a.o
> and 48-72 hours later, if successful, then
> 5. [VOTE] thread on general@i.a.o CC dev@tez and IPMC VOTE on graduation
> 6. If successful, then should be in time for the July 2014 board meeting.
>
> Cheers!
>
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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