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 226C546E2 for ; Wed, 11 May 2011 13:45:45 +0000 (UTC) Received: (qmail 43400 invoked by uid 500); 11 May 2011 13:45:44 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 43264 invoked by uid 500); 11 May 2011 13:45:44 -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 43256 invoked by uid 99); 11 May 2011 13:45:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 May 2011 13:45:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 209.85.212.43 as permitted sender) Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 May 2011 13:45:38 +0000 Received: by vws10 with SMTP id 10so429939vws.30 for ; Wed, 11 May 2011 06:45:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=qMeKXz2/m5OdDsqICPPvNTxLu1/NtR2BgjE6fVDwZ2I=; b=rpCgM7auLo/rOjHSgb5w2ocCK0MU5yMsT5txgCQVWAnM/esjmWfcjBYtPhLumFiatI qVGnmNDjXhscU8sBAd3vilQnjIsp/lt9EDxougyN7jmRNOKY5kAO2RKTZ5IzlljHoigJ /l9D41GtMEsJDU0/zO9gyRQWzqasT8QK1XhW0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VjvmNbdwxr7sHSt7EDem+D9CGo+VXJbhXMe2YMkxyMvC7lnjgZhBeHyw3NtZPiSmZF y4DnCQLq1IrT0Vkll45Yo8HEjPpX76T5/N4LLS7JrSIxY2AB+AhGCgIs2ELP0Gs0YVmK 72EPl0z8lswShiZnDbb0SDF+uOladqJh7I6WM= MIME-Version: 1.0 Received: by 10.52.177.234 with SMTP id ct10mr408199vdc.2.1305121517506; Wed, 11 May 2011 06:45:17 -0700 (PDT) Received: by 10.220.77.82 with HTTP; Wed, 11 May 2011 06:45:17 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 May 2011 14:45:17 +0100 Message-ID: Subject: Re: [OGNL] startup questions From: sebb To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 On 11 May 2011 14:36, Jochen Wiedmann wrote: > On Wed, May 11, 2011 at 2:28 PM, sebb wrote: > >> I'd be inclined to keep the current package name and Maven ids during >> (most of) incubation. > > Disagreed. Changing package names etc. should be the first steps in > incubation. As should be the publication of an early release with the > new package names. This allows end users to pick up as soon as > possible while still be upwards compatible. However, if a breaking API change is needed, then the package name/Maven ids will *have* to be changed. > If you don't do that, then users might prefer to wait "until the major > change is done". Depending on incubator code is akin to depending on alpha code, i.e. the user should be prepared for API instability. If the user is not prepared to deal with that, then they should not be using incubator code in my view. But if the OGNL developers don't mind potentially ending up with something other than o.a.c.ognl that is up to them. I'm just trying to point out that there may be disadvantages to changing now. > > > -- > I Am What I Am And That's All What I Yam (Popeye) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org