Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Pig >> mail # dev >> Next Pig release proposal

Copy link to this message
RE: Next Pig release proposal
Ref: http://tinyurl.com/4ng8upa (last discussion on 1.0)

How far have we progressed from our last discussion in March. There was no consensus on the 1.0 release. Opinions ranged from having more releases to bake in the maturity of the new parser and logical plan changes to compatibility with Hadoop API (was compared to Social Security - a very hot topic these days).

My concerns were around Hadoop API stability. I have heard that the APIs will not be stable for at least 1 year. This is taking me away from the Hadoop API stability factor (They passed healthcare in that duration. Really!) Do we want compatibility with 0.23 as a gating factor - not sure if this is anywhere close to getting done in the near future. Will we support append (0.20.205)?

Btw, Hbase has been doing 0.90.1, 0.90.2, etc. So we can take a look at this option too.


-----Original Message-----
From: Olga Natkovich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 20, 2011 4:40 PM
Subject: Next Pig release proposal


Here is what I propose we do for the next Pig release:
(1)    Branch early next week - we have major features  and many bug fixes in and will be fixing remaining bugs on the branch

(2)    Publish the release by 11/15 - that will give us a couple of weeks to stabilize the branch and get last minute bug fixes in

(3)    Make this release a 1.0 release. Reasons to go for 1.0 and not 0.10

a.       This release has minimal number of features and was focused on code stabilization and bug fixes. We believe it will be a stable release

b.      It has no major interface changes

c.       Going from 0.10 to 1.0 would be very confusing