Return-Path: X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F2888E149 for ; Tue, 15 Jan 2013 17:05:42 +0000 (UTC) Received: (qmail 41914 invoked by uid 500); 15 Jan 2013 16:53:52 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 41869 invoked by uid 500); 15 Jan 2013 16:53:51 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Received: (qmail 41795 invoked by uid 99); 15 Jan 2013 16:53:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 16:53:48 +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 (athena.apache.org: domain of bcanhome@googlemail.com designates 209.85.220.177 as permitted sender) Received: from [209.85.220.177] (HELO mail-vc0-f177.google.com) (209.85.220.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 16:53:42 +0000 Received: by mail-vc0-f177.google.com with SMTP id fo14so106579vcb.22 for ; Tue, 15 Jan 2013 08:53:21 -0800 (PST) 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=mYRIkSgqA2FDFDA1Prtwdytcszsz2aBqSL0FZ+nUSaw=; b=XJLIoEGopdlgDuO+Y607xOq0nt7Y0Ytra/14hZjAUSs5prQ2/sGkBcHSf6xy96fEhb FtnHJnkufoPX2MqWSccH/DaeBaLh8xHeRzty4v5dsNMby7z090pgvl7Qmi9hmhywbd/N 9Th4ZNZZLDYg56tFeP0fVsq9zw0uGEy5a3pOErhhq13BHq7MDphgzGt9uonq7aRLjFHp 0mXxX5oMZEwifsQv57GPTZpscEetSzyrW5vqZ6ilESNj98LbxbZq38wEFOjL/sWjfE// xcFTHC3igLu1UK00mZYCxw3EhxuKGu1aoIyFnht4kwvuqKuHzM/R/uPDHi3soKrPoCcr JpuA== MIME-Version: 1.0 Received: by 10.58.134.14 with SMTP id pg14mr109460983veb.42.1358268801498; Tue, 15 Jan 2013 08:53:21 -0800 (PST) Received: by 10.58.200.197 with HTTP; Tue, 15 Jan 2013 08:53:21 -0800 (PST) In-Reply-To: References: Date: Tue, 15 Jan 2013 17:53:21 +0100 Message-ID: Subject: Re: Create Karaf 2.4.x branch From: Achim Nierbeck To: dev@karaf.apache.org Content-Type: multipart/alternative; boundary=089e012941dc6c3d1704d3569934 X-Virus-Checked: Checked by ClamAV on apache.org --089e012941dc6c3d1704d3569934 Content-Type: text/plain; charset=ISO-8859-1 +1, and actually I think we might just skip 2.3.1 and call it a 2.4 after this one is applied :D what do you think regards, Achim 2013/1/15 Ioannis Canellos > +1 on creating a 2.4 branch. > Personally I am ok at adding new features on micro releases as long as they > don't change the API, especially considering the speed at which we bring > out new major and minor ones. > > -- > *Ioannis Canellos* > * > > ** > Blog: http://iocanel.blogspot.com > ** > Twitter: iocanel > * > -- Apache Karaf Committer & PMC OPS4J Pax Web Committer & Project Lead OPS4J Pax for Vaadin Commiter & Project Lead blog --089e012941dc6c3d1704d3569934--