From dev-return-29870-archive-asf-public=cust-asf.ponee.io@geode.apache.org Thu Oct 4 23:43:17 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B1580180658 for ; Thu, 4 Oct 2018 23:43:16 +0200 (CEST) Received: (qmail 8440 invoked by uid 500); 4 Oct 2018 21:43:15 -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 8429 invoked by uid 99); 4 Oct 2018 21:43:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2018 21:43:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5D9BFC2846 for ; Thu, 4 Oct 2018 21:43:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YsMu1VGTce7k for ; Thu, 4 Oct 2018 21:43:11 +0000 (UTC) Received: from mx0b-00296801.pphosted.com (mx0b-00296801.pphosted.com [148.163.153.148]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 999AC5F485 for ; Thu, 4 Oct 2018 21:43:10 +0000 (UTC) Received: from pps.filterd (m0114586.ppops.net [127.0.0.1]) by mx0b-00296801.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w94LgEvC013140 for ; Thu, 4 Oct 2018 21:43:09 GMT Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by mx0b-00296801.pphosted.com with ESMTP id 2mt2tgnfj3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 04 Oct 2018 21:43:08 +0000 Received: by mail-io1-f71.google.com with SMTP id k20-v6so6561811iom.22 for ; Thu, 04 Oct 2018 14:43:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=KKLuOdBHDszC+rvg8S5/WzjxjMrFyep9Ukdgq4Jx+rw=; b=KoCTRVk9sQ6HAEB+rvD4NB+MpaDyltfi3JXpxhBwjYKoc0wp77s5rCj34lXVXjsYNZ 4Pd4/n6A9eQoNtMuGBtuN1dUdnXog9z3dJTzjn6/6b1wIAn/zQ2GtuopfhCmelwWDj2H CKB1pgUaevaZbi+6Fzf/GNr+RNU4hOt3QySWjwmX056NJyO8rgs4T5E1ITWbpFY8KK4o YCiuO7sL4JcwKSQ9QcM1hWu+T2DZFl9LURR/rS8IOYguHs4AfIFZwqW8/L67ph6JqHH+ VA424P0ypuVqLjhNbFiWEydkK5C0vAZ5sQ0RXntGWwGTtomO4UWJI3SpiRxiiK3Nwu6v JD7w== X-Gm-Message-State: ABuFfohadgn+r3ktVIuzzmRerQLyk2upiFvn2EfDCbII4MFFjv2mOYgS 5frBL5Jgo9xAuzZCW2GlyTlCBEd7YJAbjHv3iJgKmiqbw3X9iKd5qE22HGMYuRFS2vUV7HGFcrz d9LoZbxfsGHiWO9BZ6FRwb7KW2j0jGgD75gkuREMDfs95oCE/bdnKnwo= X-Received: by 2002:a24:7804:: with SMTP id p4-v6mr2334178itc.123.1538689388077; Thu, 04 Oct 2018 14:43:08 -0700 (PDT) X-Google-Smtp-Source: ACcGV62s6WKwXm6JV01u8CqshaRBovbzRQMCKBgCZ0VOWoTag4lBQxpUEE0N8jDkSZzAKVIRXxXHf/xbHKhuBGmLQVk= X-Received: by 2002:a24:7804:: with SMTP id p4-v6mr2334169itc.123.1538689387742; Thu, 04 Oct 2018 14:43:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dan Smith Date: Thu, 4 Oct 2018 14:42:56 -0700 Message-ID: Subject: Re: [DISCUSS] Predictable minor release cadence To: dev@geode.apache.org Content-Type: multipart/alternative; boundary="000000000000607e2405776e0a96" X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-04_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=729 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810040195 --000000000000607e2405776e0a96 Content-Type: text/plain; charset="UTF-8" +1 I definitely like the idea of scheduled releases. I wonder if cutting the release branch a month ahead of time is overkill, but I guess we do seem to keep finding issues after the branch is cut. -Dan On Thu, Oct 4, 2018 at 1:25 PM Alexander Murmann wrote: > Hi everyone, > > I want to propose shipping Geode on a regular cadence. My concrete proposal > is to ship Geode every 3 months on the first weekday. To make sure we hit > that date we would cut the release 1 months prior to that day. > > *Why?* > Knowing on what day the release will get cut and on what day we ship allows > community members to plan their contributions. If I want my feature to be > in the next release I know by when I need to have it merged to develop and > can plan accordingly. As a user who is waiting for a particular feature or > fix that's already on develop, I know when to expect the release that > includes this work and again, can plan accordingly. > > This makes working and using Apache Geode more predictable which makes all > our lives less stressful. To make this work, it's important to be strict > about cutting the release branch on the set date and only allow critical > fixes after the release has been cut. Once we start compromising on this, > we go down a slippery slope that ultimately leads to not getting the > predictability benefits described here. > > Some other successful Apache projects share similar approaches: > > - Kafka > > releases every 4 months and cuts the release 1 month prior > - PredictionIO > releases > every 2 months > - Spark does not seem > to have a hard date, but aims to ship every 6 months, so there is at > least > a goal date > > > *What?* > As stated above, I suggest to release every three months. Given we just > shipped the next release would go out on January 2nd. That timing in > unfortunate, due to the holidays. Therefore I propose to aim for a December > 3rd (1st Monday in December) release. In order to meet that date, we should > cut the release branch on November 1st. That also means that we should > start finding a volunteer to manager the release on October 25th. I know > this seems really close, given we just shipped, but keep in mind that this > is to avoid the holidays and that we already have close to a month worth of > work on develop. > > *Proposed near future schedule:* > October 25th: Find release manager > November 1st: Cut 1.8 release branch > December 1st: Ship 1.8 > January 28th: Find release manager > February 1st: Cut 1.9 release branch > March 1st: Ship 1.9 > and so on... > > Thanks for sharing your thoughts and feedback on this! > --000000000000607e2405776e0a96--