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

Switch to Threaded View
Pig >> mail # dev >> Pig 0.13.0 release


Copy link to this message
-
Re: Pig 0.13.0 release
Releasing 0.13 and 0.10.1 is totally independent in my opinion.
It just takes the time of a committer that needs the release to happen to do it.

By minor I meant 0.13
0.10.1 is a bug fix release.
as in Major.Minor.BugFix

Our Major version is still 0

On Feb 6, 2014, at 1:43 PM, Koji Noguchi wrote:

>> To add to the discussion, I think we should release more often, based on time elapsed rather than volume of change.
>>
> I don't have preference on the frequency, but I'd like to request we make minor releases more often.
>
> At this moment, stable pig release (to me) is still 0.10.1.
> 0.11.1 and 0.12.0 both have regression bug PIG-3492 that caused multiple production pig scripts in our clusters to fail randomly.
> (unless user is disabling ColumnMapKeyPrune)
>
> If releasing 0.13 means 0.10.1 gets kicked out from the front release list, I'd like to see minor release on 0.11 or 0.12 first.
>
> Koji
>
>
>
>
> On Feb 6, 2014, at 4:25 PM, Cheolsoo Park <[EMAIL PROTECTED]>
> wrote:
>
>> +1 to 0.13 release. Why not if someone is volunteering?
>>
>> On Thu, Feb 6, 2014 at 4:06 PM, Julien Le Dem <[EMAIL PROTECTED]> wrote:
>>
>>> To add to the discussion, I think we should release more often, based on
>>> time elapsed rather than volume of change.
>>> The more often we release, the easier it is to release.
>>> Also that makes it easier for contributors to use their own contributions
>>> in official releases.
>>> It is also probably a good idea to have a clean starting point before
>>> merging the Tez branch
>>>
>>> That said, I think those changes by themselves are enough to warrant a
>>> minor release.
>>>
>>> Julien
>>>
>>> On Feb 6, 2014, at 12:24 PM, Dmitriy Ryaboy wrote:
>>>
>>>> Major updates since we release 12 that are currently in trunk:
>>>>
>>>> - lazy output (don't generate empty part files)
>>>> - jar caching optimization
>>>> - automatic local mode for small job (big wall-clock wins for long-tail
>>>> jobs)
>>>> - improved support for BigInteger, BigDecimal
>>>> - hbase loader improvements
>>>> - debug mode that leaves temp files around for examination (!)
>>>> - fixes to a few nasty bugs (PIG-3641)
>>>> - pluggable execution engine allowing work like Tez and Spork
>>>> - .. and more
>>>>
>>>> I'd say this justifies a release.
>>>>
>>>> D
>>>>
>>>>
>>>> On Wed, Feb 5, 2014 at 3:55 PM, Aniket Mokashi <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>>> List I mentioned is pending tasks before we can make a release.
>>>>>
>>>>> A complete list of contributions can be seen at -
>>>>> http://svn.apache.org/viewvc/pig/trunk/CHANGES.txt?view=markup.
>>>>>
>>>>> Some of the things that make it a good candidate for a release-
>>>>> - PIG-3419 (has several backwards incompatible api changes)
>>>>> - PIG-2672
>>>>> - PIG-3642
>>>>> - PIG-3463
>>>>> - PIG-3511
>>>>> - PIG-3657
>>>>>
>>>>> Thanks,
>>>>> Aniket
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 5, 2014 at 3:23 PM, Olga Natkovich <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>
>>>>>> Just going by the list that Aniket provided, I don't really see enough
>>>>> for
>>>>>> a full release. Two mentioned JIRAs are doc updates and one is a bug
>>> fix
>>>>>> that was ported into Pig 12.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wednesday, February 5, 2014 3:13 PM, Aniket Mokashi <
>>>>>> [EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> A good number of improvements and bug fixes have gone into trunk
>>>>> recently.
>>>>>> I'd like to know if we can roll out a Pig 0.13 release around
>>> mid-March?
>>>>>>
>>>>>> I am aware that we are planning to merge tez branch into trunk soon.
>>>>>> However, making a release before tez branch is merged will be good. Any
>>>>>> objections?
>>>>>>
>>>>>> Following are few jiras we need to wrap up before 0.13 release-
>>>>>> PIG-3591
>>>>>> PIG-3740
>>>>>> PIG-3745
>>>>>> PIG-3347
>>>>>> PIG-3731
>>>>>> Any other?
>>>>>>
>>>>>> Thanks,
>>>>>> Aniket
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> "...:::Aniket:::... Quetzalco@tl"
>>