Return-Path: Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: (qmail 59941 invoked from network); 18 Jan 2010 11:22:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Jan 2010 11:22:45 -0000 Received: (qmail 55807 invoked by uid 500); 18 Jan 2010 11:22:45 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 55756 invoked by uid 500); 18 Jan 2010 11:22:44 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 55746 invoked by uid 99); 18 Jan 2010 11:22:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2010 11:22:44 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [61.9.168.146] (HELO nskntmtas04p.mx.bigpond.com) (61.9.168.146) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2010 11:22:35 +0000 Received: from nskntotgx02p.mx.bigpond.com ([58.166.68.133]) by nskntmtas04p.mx.bigpond.com with ESMTP id <20100118112213.YEOQ21435.nskntmtas04p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com> for ; Mon, 18 Jan 2010 11:22:13 +0000 Received: from [10.0.0.10] (really [58.166.68.133]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20100118112213.QRBR5306.nskntotgx02p.mx.bigpond.com@[10.0.0.10]> for ; Mon, 18 Jan 2010 11:22:13 +0000 From: Brett Porter Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: 1.3.x branch, etc. Date: Mon, 18 Jan 2010 22:22:12 +1100 Message-Id: To: dev@archiva.apache.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150205.4B544465.0084,ss=1,fgs=0 Hi, As there have been a few things getting scheduled for 1.3.1, I created = an archiva-1.3.x branch that can be used to apply the fixes. I think the = best approach is trunk-first: ie, everything goes to trunk, and selected = issues get ported to 1.3.x (unless they only ever apply to 1.3.x). This = way, nothing ever gets missed on trunk and the need to double check all = merges is removed. I imagine the 1.3.x series to be only for a very = select number of issues, while major work occurs on trunk (a discussion = I'll start once we get past actually voting 1.3 out the door :) Any issues? Cheers, Brett -- Brett Porter brett@apache.org http://brettporter.wordpress.com/