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 Plain View
Pig >> mail # dev >> Our release process


+
Olga Natkovich 2012-11-02, 22:58
+
Alan Gates 2012-11-03, 03:19
+
Gianmarco De Francisci Mo... 2012-11-03, 17:20
+
Olga Natkovich 2012-11-05, 01:17
+
Gianmarco De Francisci Mo... 2012-11-05, 18:37
+
Olga Natkovich 2012-11-05, 18:48
+
Gianmarco De Francisci Mo... 2012-11-05, 19:34
+
Jonathan Coveney 2012-11-06, 00:53
+
Alan Gates 2012-11-06, 02:12
+
Jonathan Coveney 2012-11-07, 02:34
+
Santhosh M S 2012-11-19, 23:48
Copy link to this message
-
Re: Our release process
Hi Santhosh,

Can you clarify why running e2e tests on every checking is a problem?

Olga
________________________________
From: Santhosh M S <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Sent: Monday, November 19, 2012 3:48 PM
Subject: Re: Our release process

The push for an upgrade will work only if the higher release is backward compatible with the lower release. If not, folks will tend to use private branches. Having a stable branch on a large deployment is a good indicator of stability. However, please note that there have been instances where some releases were never adopted. I will be extremely careful in applying the rule of running e2e tests for every commit to a released branch.

If we release every quarter (hopefully) and preserve backward compatibility then I am +1 to the proposal. If the backward compatibility is not preserved then I am -1 for having to run e2e for every commit to a released branch.

Santhosh
________________________________
From: Jonathan Coveney <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Sent: Tuesday, November 6, 2012 6:34 PM
Subject: Re: Our release process

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 here), then it goes in anyway (and in some cases,
would go into 0.9 etc).

Olga is saying that for existing release (0.9, 0.10), we should only commit
P1 bug fixes there. This makes sense to me, as we're fixing the "official
release" in place.

IMHO, this would encourage people to use newer release (as this is where
the latest and greatest stuff is, including non-critical bug fixes). Olga's
criteria is a pretty clear barrier for inclusion into these releases. With
old releases, I think the key is really that they keep doing what they have
always done. Most bugs are well understood by now, and the ones that aren't
will no doubt be P1.

I'm not decided (thus no formal +1 or whatnot), but Olga's point seems
pretty reasonable to me, especially given that trunk has pretty liberal
development. Once it gets tidied up, I can understand not wanting to jostle
it.
2012/11/5 Alan Gates <[EMAIL PROTECTED]>

> 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 Coveney wrote:
>
> > 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 Gianmarco De Francisci Morales <[EMAIL PROTECTED]>
> >
> >> Hi,
> >>
> >> On Mon, Nov 5, 2012 at 10:48 AM, Olga Natkovich <[EMAIL PROTECTED]>
> >> 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 failures with no easy workaround
> >>>
> >>
> >> Thanks Olga, now I get what you mean.
> >> I don't have a strong opinion on this.
> >> On one hand I see why you don't want to put too many patches in the
> >> branches in order to keep things stable.
> >> On the other hand when we do a 0.10.x release with x>0 the users would
> >> like to have as many bugs fixed as possible.
> >>
> >>> Regarding tests. I would suggest we have different rules for trunk and
> >> branches:
> >>>
> >>> (1) For branches, I think we should run the full regression suite
> >> (including e2e) prior to commit. This way we can ensure branch stability
+
Santhosh M S 2012-11-26, 08:00
+
Olga Natkovich 2012-11-26, 17:38
+
Santhosh M S 2012-11-30, 07:16
+
Julien Le Dem 2012-12-01, 01:37
+
Santhosh M S 2012-12-01, 07:46
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