From dev-return-31737-archive-asf-public=cust-asf.ponee.io@geode.apache.org Tue Aug 27 02:44:49 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id AB118180645 for ; Tue, 27 Aug 2019 04:44:48 +0200 (CEST) Received: (qmail 81792 invoked by uid 500); 27 Aug 2019 02:44:48 -0000 Mailing-List: contact dev-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list dev@geode.apache.org Received: (qmail 81781 invoked by uid 99); 27 Aug 2019 02:44:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Aug 2019 02:44:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 103311A343B for ; Tue, 27 Aug 2019 02:44:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Kp1P7WGEOT9s for ; Tue, 27 Aug 2019 02:44:42 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=148.163.150.38; helo=mx0a-00296801.pphosted.com; envelope-from=jbarrett@pivotal.io; receiver= Received: from mx0a-00296801.pphosted.com (mx0a-00296801.pphosted.com [148.163.150.38]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id EE233BC7F0 for ; Tue, 27 Aug 2019 02:44:41 +0000 (UTC) Received: from pps.filterd (m0114583.ppops.net [127.0.0.1]) by mx0a-00296801.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7R2fKRR011582 for ; Tue, 27 Aug 2019 02:44:40 GMT Received: from mail-pl1-f198.google.com (mail-pl1-f198.google.com [209.85.214.198]) by mx0a-00296801.pphosted.com with ESMTP id 2ujv0p1xxx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Tue, 27 Aug 2019 02:44:40 +0000 Received: by mail-pl1-f198.google.com with SMTP id go13so11156896plb.10 for ; Mon, 26 Aug 2019 19:44:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=zZs4mTsxk/DIyfCKPrOvswp4TleSHOqKDVyJAvhCYkA=; b=GKa+/tlOv5OOASM4zHEavGWEsG4/OWv5kNdPOdC9sC7Jiml6KZg69Goz4esd65/+oe PQk+MKLrn/B727pVgdnkzr7qFOGQLl3bpmkukvNXbDVdsejOHo3RnL3L7XNYm14Qg+LM cqDOaSn03PsMrWJkovqyD7WCroPe37bLlcwVklATDvogA2EL0xBGZx478OJeW2ppKrZo C+25xYmT8BxZxTTktaCmChZLyYIsEp8oULLkCNZa6nPgQOG3Z/L8l2AJWG+5dnnACtsF V/E5Kq3RIN2IPh2DgjYLSH8U1ymKQg754BMPlsQrUfcgzY6vQGCwhoMp2f9ARvptho5t +BcQ== X-Gm-Message-State: APjAAAX/eik3ilQGVPQFCbuVcRfjgxpFYwDpUf1TpTnQ6w9X6yPEi4MP 6qoGwlXrOMqhZX/tRAsAsAdyE68rsqVMCdYPrYb7RVRImVtuYPYnIptj9PBWY7LNDxvYtgXgO+F RnF/IEUoDTNd82LA5n7dyE1p/OLhJnxj5LXc8lx4= X-Received: by 2002:a65:47c1:: with SMTP id f1mr18956821pgs.169.1566873879193; Mon, 26 Aug 2019 19:44:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqyVRU0ti1pa1GXBOBCMDFtTbXTyLoVTni5xMI8vI4cAMLvRkaAXZoq7Pt44V9WnRuq8FmV1Fw== X-Received: by 2002:a65:47c1:: with SMTP id f1mr18956798pgs.169.1566873878695; Mon, 26 Aug 2019 19:44:38 -0700 (PDT) Received: from jacobs-mbp.users.condointernet.net ([174.127.212.211]) by smtp.gmail.com with ESMTPSA id a128sm17541896pfb.185.2019.08.26.19.44.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Aug 2019 19:44:38 -0700 (PDT) From: Jacob Barrett Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [DISCUSS] Pulling the current proposed 1.10 release until we can agree on develop being stable Date: Mon, 26 Aug 2019 19:44:37 -0700 References: <0b51b0d6-de90-b8f0-0ae1-d0b8fcc0587f@apache.com> To: dev@geode.apache.org In-Reply-To: <0b51b0d6-de90-b8f0-0ae1-d0b8fcc0587f@apache.com> Message-Id: X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-26_08:2019-08-26,2019-08-26 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 lowpriorityscore=0 malwarescore=0 suspectscore=1 mlxlogscore=999 mlxscore=0 bulkscore=0 priorityscore=1501 spamscore=0 clxscore=1015 phishscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908270028 While I share your concern that too many things are getting = cherry-picked into the release, I disagree that recutting the branch is = a good solution. Recutting the branch effectively cherry-picks = everything on the develop branch. This means we start at ground zero = evaluating this release.=20 Each code change brings risk. We minimize that risk by reducing the = change on the release branch. The alternative is to =E2=80=9Clock=E2=80=9D= the develop branch, but this slows productivity significantly.=20 I do think we could do a better job vetting what is and isn=E2=80=99t = critical to the release though. I would like to see a harder line on new = bugs vs. old bugs. Fixes to bugs introduced in this release are a clear = candidate for including in the release. Bugs that have existed for = several releases should probably get bumped with consideration given for = likely or present impact to a user and complexity of the issue and fix. -Jake > On Aug 26, 2019, at 4:06 PM, Udo Kohlmeyer wrote: >=20 > Hi there Apache Geode devs, >=20 > It has been some weeks since the proposed 1.10 release was cut. We've = gone through a few cycles where we keep on submitting "please include = ticket GEODE-XXX" because it is critical and will break the system. = WHICH in reality tells me that current develop is broken and unstable. >=20 > I'm going to suggest that we abandon the current 1.10 release branch. = I cannot shake the feeling that our continuous cherry picking into a = branch will result in either the branch becoming unmaintainable, given = we have only select fixes in the branch OR we end up with a branch that = is more stable than our current development branch, which would result = in us having to rebase the develop branch onto the 1.10 branch. >=20 > I propose that once we see the pipeline is clean and green for a solid = we then again attempt to cut 1.10 branch. >=20 > We CANNOT continue adding to a branch in order to stabilize it.. It = just means the branch we cut from is unstable. If we cannot cut a branch = from develop without having to have weeks of stabilization cycles, then = our main branch is broken... >=20 > Either way, not a good spot to be in. >=20 > Thoughts? >=20 > --Udo >=20