or failing silently.
Does that work for?
Santhosh
From: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org
Sent: Monday, December 17, 2012 4:16 PM
Subject: Re: Our release process
Hi Jonathan,
I thought I answered your email last week
in this respect.
Olga
From: Jonathan Coveney jcove...@gmail.com
To: dev@pig.apache.org dev@pig.apache.org; Olga Natkovich
onatkov...@yahoo.com
Sent: Thursday, December 13, 2012 1:14 PM
Subject: Re: Our release process
Olga,
A related but separate question: what do y'all
need a private branch if our rules are too
relaxed.
Olga
- Original Message -
From: Julien Le Dem jul...@twitter.com
To: dev@pig.apache.org dev@pig.apache.org; Olga Natkovich
onatkov...@yahoo.com
Cc:
Sent: Wednesday, December 12, 2012 4:54 PM
Subject: Re: Our release process
Agreed
are too relaxed.
Olga
- Original Message -
From: Julien Le Dem jul...@twitter.com
To: dev@pig.apache.org dev@pig.apache.org; Olga Natkovich
onatkov...@yahoo.com
Cc:
Sent: Wednesday, December 12, 2012 4:54 PM
Subject: Re: Our release process
Agreed. The priority of a change
@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com; billgra...@gmail.com billgra...@gmail.com
Sent: Friday, December 7, 2012 3:54 PM
Subject: Re: Our release process
Here's my criteria for inclusion in a release branch:
- no new feature. Only bug fixes
@pig.apache.org dev@pig.apache.org
Sent: Wednesday, December 12, 2012 10:26 AM
Subject: Re: Our release process
I think we all agree here, let's not jump to conclusions.
Everything in this branch I am talking about is in Apache Pig. Everything
we do in Pig is contributed.
We have a branch for 0.11 where we
: Wednesday, December 12, 2012 10:26 AM
Subject: Re: Our release process
I think we all agree here, let's not jump to conclusions.
Everything in this branch I am talking about is in Apache Pig. Everything
we do in Pig is contributed.
We have a branch for 0.11 where we keep merging the official
@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com; billgra...@gmail.com billgra...@gmail.com
Sent: Friday, December 7, 2012 3:54 PM
Subject: Re: Our release process
Here's my criteria for inclusion in a release branch:
- no new feature. Only bug fixes
From: Julien Le Dem jul...@twitter.com
To: Olga Natkovich onatkov...@yahoo.com
Cc: dev@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com; billgra...@gmail.com billgra...@gmail.com
Sent: Friday, December 7, 2012 3:54 PM
Subject: Re: Our release process
Here's my
, 2012 11:46 PM
*Subject:* Re: Our release process
HI Julien,
You are making most of the points that I did on this thread (CI for e2e,
not burdening clean e2e prior to every commit for a release branch). The
only point on which there is no clear agreement is the definition of a bug
that can
...@gmail.com
Sent: Friday, November 30, 2012 11:46 PM
Subject: Re: Our release process
HI Julien,
You are making most of the points that I did on this thread (CI for e2e, not
burdening clean e2e prior to every commit for a release branch). The only point
on which there is no clear agreement
29, 2012 9:45 AM
Subject: Re: Our release process
The release branch receives only bug fixes. Patch level releases (3rd
version number) are issued out of the release branch and introduce
only bug fixes and no new features.
Deciding whether a patch is applied to the release branch is based
; Santhosh M S santhosh_mut...@yahoo.com
Cc: billgra...@gmail.com billgra...@gmail.com
Sent: Friday, November 30, 2012 5:37 PM
Subject: Re: Our release process
Proposed criteria:
- it makes the tests fail. targets test-commit + test + e2e tests
- a critical bug is reported in a short time frame
making it
harder to develop.
Santhosh
From: Bill Graham billgra...@gmail.com
To: dev@pig.apache.org
Sent: Wednesday, November 28, 2012 11:39 AM
Subject: Re: Our release process
I agree releasing often is ideal, but releasing major versions once a month
: Thursday, November 29, 2012 9:45 AM
Subject: Re: Our release process
The release branch receives only bug fixes. Patch level releases (3rd
version number) are issued out of the release branch and introduce
only bug fixes and no new features.
Deciding whether a patch is applied to the release branch
From: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com
Sent: Tuesday, November 27, 2012 10:41 AM
Subject: Re: Our release process
Hi Santhosh,
What is your definition of P2s?
Olga
- Original
: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com
Sent: Tuesday, November 27, 2012 10:41 AM
Subject: Re: Our release process
Hi Santhosh,
What is your definition of P2s?
Olga
- Original Message
: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com
Sent: Tuesday, November 27, 2012 10:41 AM
Subject: Re: Our release process
Hi Santhosh,
What is your definition of P2s?
Olga
- Original Message
Hi Santhosh,
What is your definition of P2s?
Olga
- Original Message -
From: Santhosh M S santhosh_mut...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org; Olga Natkovich
onatkov...@yahoo.com
Cc:
Sent: Monday, November 26, 2012 11:49 PM
Subject: Re: Our release process
Hi Olga
,
Santhosh
From: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com
Sent: Tuesday, November 27, 2012 10:41 AM
Subject: Re: Our release process
Hi Santhosh,
What is your definition of P2s?
Olga
From: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org; Santhosh M S
santhosh_mut...@yahoo.com
Sent: Sunday, November 25, 2012 5:56 PM
Subject: Re: Our release process
Hi Santhosh,
Can you clarify why running e2e tests on every checking
.
Olga
From: Santhosh M S santhosh_mut...@yahoo.com
To: Olga Natkovich onatkov...@yahoo.com; dev@pig.apache.org
dev@pig.apache.org
Sent: Monday, November 26, 2012 12:00 AM
Subject: Re: Our release process
It takes too long to run. If the e2e tests are run
developers to fix issues of significance
without impacting stability.
Thanks,
Santhosh
From: Olga Natkovich onatkov...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org
Sent: Monday, November 26, 2012 9:38 AM
Subject: Re: Our release process
Hi Santhosh,
I
Hi Santhosh,
Can you clarify why running e2e tests on every checking is a problem?
Olga
From: Santhosh M S santhosh_mut...@yahoo.com
To: dev@pig.apache.org dev@pig.apache.org
Sent: Monday, November 19, 2012 3:48 PM
Subject: Re: Our release process
The push
then I am -1 for having to run e2e for every commit to a released branch.
Santhosh
From: Jonathan Coveney jcove...@gmail.com
To: dev@pig.apache.org dev@pig.apache.org
Sent: Tuesday, November 6, 2012 6:34 PM
Subject: Re: Our release process
I think it might
I think it might be good to clarify (for me) a couple of cases:
1. we have branched a new release
2. an existing release
The way I understand things, in the case of 1, we have a backlog of patches
(not all of which are P1 bugs), and that's ok. If a new bad bug comes in
(the subject of debate
From: Alan Gates ga...@hortonworks.com
To: dev@pig.apache.org
Sent: Friday, November 2, 2012 8:19 PM
Subject: Re: Our release process
I am all for maintaining stability of branches, and the trunk, as everyone
benefits from it. But I do not think this means we should limit bug fixing
quickly when
things break.
Olga
From: Gianmarco De Francisci Morales g...@apache.org
To: dev@pig.apache.org; Olga Natkovich onatkov...@yahoo.com
Sent: Monday, November 5, 2012 10:37 AM
Subject: Re: Our release process
Hi,
Sure we don't want to commit patches
Hi,
On Mon, Nov 5, 2012 at 10:48 AM, Olga Natkovich onatkov...@yahoo.com wrote:
Hi Gianmarco,
Thanks for your comments. Here is a little more information.
At Yahoo, we consider the following issues to be P1:
(1) Bugs that cause wrong results being produced silently
(2) Bugs that cause
This seems to make sense to me. People can always back-port features, and
this encourages them to use the newer ones. It also means we will be more
rigorous about stability, which is good as it is a big plus for Pig. I
think for older branches, stability trumps features in a big way.
2012/11/5
Jonathan, for clarity, are you saying you agree that we should only put bug
fixes in branches or we should only put high priority bug fixes in branches? I
think we all agree on the former, but there appear to be different views on the
latter.
Alan.
On Nov 5, 2012, at 4:53 PM, Jonathan
From: Alan Gates ga...@hortonworks.com
To: dev@pig.apache.org
Sent: Friday, November 2, 2012 8:19 PM
Subject: Re: Our release process
I am all for maintaining stability of branches, and the trunk, as everyone
benefits from it. But I do not think this means we should limit bug fixing
Hi,
I agree with what Alan says and I like his proposal.
However, to make it feasible, we need to make jenkins builds stable,
otherwise a real problem introduced by a patch might be lost in the
hundreds of failures due to clover licenses, minicluster issues, etc...
I don't like too much making
Hi guys,
Mid next year, we agreed on a release process documented in this thread:
http://www.mail-archive.com/dev@pig.apache.org/msg04172.html.
Since then, we have not really followed either of its two rules:
(1) Frequent (every 3 month releases)
(2) Branch stability (only P1 issues on the
I am all for maintaining stability of branches, and the trunk, as everyone
benefits from it. But I do not think this means we should limit bug fixing in
the branches to only critical issues. As Pig gets more users we have more and
more people on older branches who will want fixes for bugs
35 matches
Mail list logo
