Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 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
Based on the discussion - there does not seem to be a disagreement on the first 2 points but we still don't have a consensus on the version number. The problem is that we can't branch till we do.

I am going to send a separate email on the vote for the version number. According to our bylaws, we need Lazy Majority from Committers and the vote lasts 3 days.

Olga

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

Hi,

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

Comments?

Olga
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB