Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 061FD10F20 for ; Sun, 3 May 2015 21:37:53 +0000 (UTC) Received: (qmail 75877 invoked by uid 500); 3 May 2015 21:37:51 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 75817 invoked by uid 500); 3 May 2015 21:37:51 -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 75806 invoked by uid 99); 3 May 2015 21:37:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 May 2015 21:37:51 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.191.145.13 which is an MX secondary for log4j-dev@logging.apache.org) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 May 2015 21:37:46 +0000 Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 826D624B3F for ; Sun, 3 May 2015 21:37:26 +0000 (UTC) Received: by wizk4 with SMTP id k4so102799832wiz.1 for ; Sun, 03 May 2015 14:37:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6fvS+Q0IIS8u9yR9Xtg8vL/GpX89Wg4NFOKLwQBdVxs=; b=oV9MFNcA2a+vJGh0eXDnt2uEXvcEmbTM4VmKJ7n+gdEu8Kel2lukqTYajKno/VvBth fslqzU5x3WE2DzLync3IA2Qb08xIsSVR8g/5NNy1Bvb0m73O4LwLL7YlVjjqkXWJSE6u TQHJAZfb1uO8Aq2tj3iSTGgRze+CRX90YA8/TuvvxA2NGz2yoXuAmsNZ+GbpW91UQfe5 dF5bReHp92VDuTlLpyICJS8wRjfHN6r5ZFFhrpiumTyu5CeGpAdScyqkjlHy0hHnLllg F8DvwMQi2T8TKqpKKfkbZFDg98UnAWwItQA0tRuzOypR+y4f9NkMcFMlj5GV5N5uAJNP AE1A== MIME-Version: 1.0 X-Received: by 10.194.77.7 with SMTP id o7mr35440546wjw.95.1430689039454; Sun, 03 May 2015 14:37:19 -0700 (PDT) Received: by 10.27.83.211 with HTTP; Sun, 3 May 2015 14:37:19 -0700 (PDT) In-Reply-To: <9DAAD84B-BEC5-471B-8DE4-B16F8F7A88F0@dslextreme.com> References: <9DAAD84B-BEC5-471B-8DE4-B16F8F7A88F0@dslextreme.com> Date: Sun, 3 May 2015 14:37:19 -0700 Message-ID: Subject: Re: Short term road map? From: Gary Gregory To: Log4J Developers List Content-Type: multipart/alternative; boundary=047d7bfd05fcfb17920515343f1f X-Virus-Checked: Checked by ClamAV on apache.org --047d7bfd05fcfb17920515343f1f Content-Type: text/plain; charset=UTF-8 OK, I recall that, right! To in more concrete terms: 2.3: ASAP with Jenkins resovled. 2.4: Immediately after 2.3 but with Java 7, nothing else. Kinda makes the Java 6 apples and Java 7 oranges easier to compare. 2.4.1/2.5 and on: Using Java 7 features. ? Gary On Sun, May 3, 2015 at 11:45 AM, Ralph Goers wrote: > Unless we actually change the API I see no reason to call it 3.0 even if > we upgrade the minimum JDK. The release notes have made it clear that the > change is coming. > > Ralph > > On May 3, 2015, at 11:06 AM, Gary Gregory wrote: > > If I had the time to do releases, I would propose: > > - Release 2.3 ASAP. Perhaps as soon as the Jenkins issue is resolved or a > workaround documented. We have plenty of fixes for a 2.3. > > - Depend on Java 7 and release the same code as 2.3. Personally, I would > call this 3.0 to make it clear the platform change is important (see below) > This leave room in the 2.3.x line for Java 6 releases if needed. > > Then release a 3.0.1 that actually takes advantage of: try-with-resources, > String switch, diamond notation. any Java 7-only APIs (NIO 2.0), updated > dependencies, file change notification for configuration updates, and so on. > > The Java 7 based release could also be called 2.4 for the more > conservative. > > Thoughts? > Gary > > -- > E-Mail: garydgregory@gmail.com | ggregory@apache.org > Java Persistence with Hibernate, Second Edition > > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > > > -- E-Mail: garydgregory@gmail.com | ggregory@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --047d7bfd05fcfb17920515343f1f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
OK, I recall that, right!

To in more co= ncrete terms:

2.3: ASAP with Jenkins resovled.
2.4: Immediately after 2.3 but with Java 7, nothing else. Kinda make= s the Java 6 apples and Java 7 oranges easier to compare.
2.4.1/2= .5 and on: Using Java 7 features.

?

=
Gary

On Sun, May 3, 2015 at 11:45 AM, Ralph Goers &l= t;ralph.goe= rs@dslextreme.com> wrote:
<= div style=3D"word-wrap:break-word">
Unless we actually change the API I= see no reason to call it 3.0 even if we upgrade the minimum JDK.=C2=A0 The= release notes have made it clear that the change is coming.

Ralph

On M= ay 3, 2015, at 11:06 AM, Gary Gregory <garydgregory@gmail.com> wrote:

<= div>
If I had the time to do releases, I would propose:
- Release 2.3 ASAP. Perhaps as soon as the Jenkins issue is= resolved or a workaround documented. We have plenty of fixes for a 2.3.

- Depend on Java 7 and release the same code as 2.3.= Personally, I would call this 3.0 to make it clear the platform change is = important (see below) This leave room in the 2.3.x line for Java 6 releases= if needed.

Then release a 3.0.1 that actually tak= es advantage of: try-with-resources, String switch, diamond notation. any J= ava 7-only APIs (NIO 2.0), updated dependencies, file change notification f= or configuration updates, and so on.





--
--047d7bfd05fcfb17920515343f1f--