Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-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 42DA217741 for ; Thu, 19 Feb 2015 22:52:13 +0000 (UTC) Received: (qmail 54676 invoked by uid 500); 19 Feb 2015 22:52:13 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 54547 invoked by uid 500); 19 Feb 2015 22:52:12 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 54535 invoked by uid 99); 19 Feb 2015 22:52:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 22:52:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of benjamin.j.mccann@gmail.com designates 209.85.213.177 as permitted sender) Received: from [209.85.213.177] (HELO mail-ig0-f177.google.com) (209.85.213.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 22:51:48 +0000 Received: by mail-ig0-f177.google.com with SMTP id z20so13126918igj.4 for ; Thu, 19 Feb 2015 14:51:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=XkcI3nTdlsaDIIWw09gAMqbox7SRdzg1JaUIX7WRfiI=; b=jB/FtVHsQG92Odpih9WsoZ2hRL3aCkpV0m0pDzB3295/mk94kTHwBlKzHT1br4lGHA osvKkQVMY3P84sgIeTHfah7KW8PWRbz38dGdODlXPbCHCX4/yiGawhqF9rpgmgbafIXq aZn40g55DXPbOAbvA4YGUoP+GDGvLYUbRpOzye0vccVgwUqHKAz4qWt1VL9kxXsv5RIq 1X0Zv2MXC7cdzNa1FFGavG3dMrWdCnElfdiw5/Gi7HneBrjnjPng382cpz9rpFjJMAEu GjJOmPuFAp7SFCplz1C10xR0nEBTZmXu1G4umoSO5HtjxydjJb5UZAgtD/26jfAyIvO9 MloA== MIME-Version: 1.0 X-Received: by 10.50.97.41 with SMTP id dx9mr8067404igb.1.1424386261364; Thu, 19 Feb 2015 14:51:01 -0800 (PST) Sender: benjamin.j.mccann@gmail.com Received: by 10.36.9.73 with HTTP; Thu, 19 Feb 2015 14:51:00 -0800 (PST) Received: by 10.36.9.73 with HTTP; Thu, 19 Feb 2015 14:51:00 -0800 (PST) In-Reply-To: References: <54266C37.70006@apache.org> <543590CA.1030201@apache.org> <543596F3.6040109@apache.org> <1423459778215-4672634.post@n4.nabble.com> <54D8628A.5030708@apache.org> <54E5EE89.1060503@apache.org> <54E5FBDF.8040100@apache.org> Date: Thu, 19 Feb 2015 14:51:00 -0800 X-Google-Sender-Auth: dNFv_cAvg0YPqMjHSAQHiawWpo8 Message-ID: Subject: Re: [VOTE] Release BCEL 6.0 based on RC3 From: Ben McCann To: Commons Developers List Content-Type: multipart/alternative; boundary=047d7b10cd5321d184050f78c5d4 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10cd5321d184050f78c5d4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Is BCEL-209 the only pending issue that would break binary compatibility? Perhaps we could prioritize the issues that would break compatibility. On Thu, Feb 19, 2015 at 7:19 AM, Benedikt Ritter wrote= : > 2015-02-19 16:14 GMT+01:00 Ben McCann : > > > Why do you say users would have to rename all their import statements? Is > > there a patch pending that we're consider which would change the packag= e > > name? I don't think there'd be any changes that be hard for end users t= o > > deal with that I'm aware of. > > > > Changing the major version number for a commons component always implies > changing maven coords and the package name. No, it does not. We can release a new major version without a new package name and new maven coords IFF the new version is binary compatible. Gary > We do this, so that several > versions of the same commons component can be in the same classpath. > > Benedikt > > > > > > On Thu, Feb 19, 2015 at 7:07 AM, Benedikt Ritter > > wrote: > > > > > 2015-02-19 16:06 GMT+01:00 Emmanuel Bourg : > > > > > > > Le 19/02/2015 15:17, Ben McCann a =C3=A9crit : > > > > > Perhaps if there are only a few breaking changes we could > prioritize > > > > > reviewing those first and leave the rest for 6.1. Alternatively, > we > > > > could > > > > > release what's available now as 6.0 and release all the patches i= n > a > > > > couple > > > > > months as 7.0. > > > > > > > > I wouldn't force our users to rename all their import statements in a > > > > couple of month as we release BCEL 7.0 with breaking changes becaus= e > we > > > > didn't want to handle a known issue for BCEL 6.0. > > > > > > > > Let's settle this now. > > > > > > > > > > +1 > > > > > > > > > > > > > > Emmanuel Bourg > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > > > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > > > > > > > > > > > -- > > > http://people.apache.org/~britter/ > > > http://www.systemoutprintln.de/ > > > http://twitter.com/BenediktRitter > > > http://github.com/britter > > > > > > > > > > > -- > > about.me/benmccann > > > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- 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 --047d7b10cd5321d184050f78c5d4--