Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1B1EF200B6B for ; Fri, 9 Sep 2016 20:13:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 19A82160AA3; Fri, 9 Sep 2016 18:13:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3B939160AC2 for ; Fri, 9 Sep 2016 20:13:51 +0200 (CEST) Received: (qmail 42490 invoked by uid 500); 9 Sep 2016 18:13:50 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 42480 invoked by uid 99); 9 Sep 2016 18:13:50 -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; Fri, 09 Sep 2016 18:13:50 +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 F2B51C0C0A for ; Fri, 9 Sep 2016 18:13:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id yliwheFVjTSd for ; Fri, 9 Sep 2016 18:13:47 +0000 (UTC) Received: from mail-vk0-f53.google.com (mail-vk0-f53.google.com [209.85.213.53]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id DA9BD5FBB1 for ; Fri, 9 Sep 2016 18:13:46 +0000 (UTC) Received: by mail-vk0-f53.google.com with SMTP id m62so21396566vkd.3 for ; Fri, 09 Sep 2016 11:13:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=iQ4+C4rJQD00TU1ApvWrH/iuF78x/tfzHJtDEIen2Ys=; b=RtocrQJFXUwUG7lps0V8rKV6xYbHsT5I+GtFbfJLMEEIH8RUXijdS9cakOFFdSEVUF VqNoVNdKahxBsuBc4WaPtp/jFRjsXY9vZozkfqZPyxRzgpjbtvyDmMo0mutbdedXPVCU d077CAGTaOiD54VHGHaVjbW8QUXkDNbpg8K6pvs6S68iP9RpXsdazcQ8XlN8eCytbjgU RMgLzWMCZ9qWJ1OdhS27eIaA5jO6jz3FuLpC9RxD6PZuuv9EGViLnepo0ckdfhut7NFM 9MVcAh+Otyjs7C4oAK/+hyNWa5rJ39VOX/sQcuA/kFdlVOBa67kfxT1EsOyqC6Jo0FbN lkyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=iQ4+C4rJQD00TU1ApvWrH/iuF78x/tfzHJtDEIen2Ys=; b=BByQcQ2LoWbxkJZAjF9wliI2+9vFO7jqySATmh1dEcPy2jF+DRRHEYIyRdVzvM5OKx C8WdOBCngE1X9lLxQez+IwqdcNuu2dcMagW5fxRfYUY8hPa+yfPM5DQBP6hm1QRO5pMR b4LhzPFkw3a04vBDrgw8bXtgBnqb6tX04UZ2nmlPceDl9OmJK/UjQRtwKc5ALAxslbSp kIIRoHgO5lkgKG3F/1FsYo8A10wJzYWenwBYr4Huuw/Y/zrklWZFVXCiCYlONg3uEuBK 3s9F7cAuuipJdmla2xZKtQCFckUuyZGXapqKijZnFAGwN+qlhdYGtOjxL64/g3k2JMpa STKw== X-Gm-Message-State: AE9vXwMxEL8sTBL2BrWxnLG4YvDQGQ6cQ28SR5wgWDp2A0YuNLtIcQe4pllcZrF0c3UNNkYdCenYIWTKUwEsnw== X-Received: by 10.31.85.196 with SMTP id j187mr3398306vkb.12.1473444826154; Fri, 09 Sep 2016 11:13:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.111.133 with HTTP; Fri, 9 Sep 2016 11:13:45 -0700 (PDT) In-Reply-To: References: From: Matt Sicker Date: Fri, 9 Sep 2016 13:13:45 -0500 Message-ID: Subject: Re: Release process To: Log4J Developers List Content-Type: multipart/alternative; boundary=001a114e51d67597e9053c171b92 archived-at: Fri, 09 Sep 2016 18:13:52 -0000 --001a114e51d67597e9053c171b92 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Are we all caught up with the desired branches we wanted merged? On 9 September 2016 at 13:08, Remko Popma wrote: > What is our thinking on this for the upcoming release? > > On Fri, Sep 2, 2016 at 8:22 PM, Mikael St=C3=A5ldal > wrote: > >> On LOG4J2-1548, Remko Popma >> >> wrote: >> >> I'm okay with changing the process but we need to think through the >>> implications of maintaining multiple branches. I don't mind fixing a bu= g >>> in, say, the 2.7.x maintenance branch and merging that fix also into th= e >>> 2.8 new features branch, but what do we do with subsequent releases? >>> Once we are on version 2.10, and we receive a bug report against versio= n >>> 2.7, do we add a fix to the maintenance branches 2.7.x, 2.8.x and 2.9.x= in >>> addition to the 2.10 new feature branch? When do we stop supporting old >>> maintenance branches? >>> >> >> I think we should make sure that we can always easily make patch release= s >> on the latest minor release (like 2.6.3 now), and do so whenever a serio= us >> bug is discovered and fixed (like LOG4J-1548). >> >> I don't think that we should normally make patch releases on older minor >> releases (like 2.5.1 now) though. That should only be done in exceptiona= l >> cases, and we should not prepare for it any more than keeping a tag for >> each release in Git. >> >> I also think that we should consider ways of reducing the number of >> serious issues introduced in minor releases, such as making a public bet= a >> release before a minor release. (I was not really satisfied with the >> quality of the 2.6 release, and I think we should try to do better in th= e >> future.) >> >> -- >> [image: MagineTV] >> >> *Mikael St=C3=A5ldal* >> Senior software developer >> >> *Magine TV* >> mikael.staldal@magine.com >> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >> >> Privileged and/or Confidential Information may be contained in this >> message. If you are not the addressee indicated in this message >> (or responsible for delivery of the message to such a person), you may >> not copy or deliver this message to anyone. In such case, >> you should destroy this message and kindly notify the sender by reply >> email. >> > > --=20 Matt Sicker --001a114e51d67597e9053c171b92 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Are we all caught up with the desired branches we wanted m= erged?

On 9 = September 2016 at 13:08, Remko Popma <remko.popma@gmail.com> wrote:
What is our = thinking on this for the upcoming release?

On F= ri, Sep 2, 2016 at 8:22 PM, Mikael St=C3=A5ldal <mikael.staldal@ma= gine.com> wrote:
On LOG4J2-1548,=C2=A0Remko Popma=C2=A0wrote:

= I'm okay with changing the process=20 but we need to think through the implications of maintaining multiple=20 branches. I don't mind fixing a bug in, say, the 2.7.x maintenance=20 branch and merging that fix also into the 2.8 new features branch, but=20 what do we do with subsequent releases?
Once we are on version 2.10, and= we receive a bug report against=20 version 2.7, do we add a fix to the maintenance branches 2.7.x, 2.8.x=20 and 2.9.x in addition to the 2.10 new feature branch? When do we stop=20 supporting old maintenance branches?

I = think we should make sure that we can always easily make patch releases on = the latest minor release (like 2.6.3 now), and do so whenever a serious bug= is discovered and fixed (like LOG4J-1548).

I don&= #39;t think that we should normally make patch releases on older minor rele= ases (like 2.5.1 now) though. That should only be done in exceptional cases= , and we should not prepare for it any more than keeping a tag for each rel= ease in Git.

I also think that we should consider = ways of reducing the number of serious issues introduced in minor releases,= such as making a public beta release before a minor release. (I was not re= ally satisfied with the quality of the 2.6 release, and I think we should t= ry to do better in the future.)
=C2=A0
--
<= div dir=3D"ltr">
3D"MagineTV"

Mikael St=C3=A5ldal
Senior software developer

Magine TV
mikael.s= taldal@magine.com=C2=A0 =C2=A0=C2=A0
Grev Turegatan 3 =C2=A0|=C2=A0114 46 St= ockholm, Sweden=C2=A0 | =C2=A0 www.magine.com

Privilege= d and/or Confidential Information may be contained in this message. If=20 you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,=C2=A0
you should destroy this message and kindly notify the sender by reply ema= il. =C2=A0=C2=A0




--
=
Matt Sick= er <boards@gmail.c= om>
--001a114e51d67597e9053c171b92--