Return-Path: Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: (qmail 87760 invoked from network); 26 Sep 2010 20:20:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Sep 2010 20:20:22 -0000 Received: (qmail 94725 invoked by uid 500); 26 Sep 2010 20:20:21 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 94440 invoked by uid 500); 26 Sep 2010 20:20:20 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 94432 invoked by uid 99); 26 Sep 2010 20:20:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Sep 2010 20:20:20 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andreas.veithen@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qy0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Sep 2010 20:20:12 +0000 Received: by qyk5 with SMTP id 5so6684245qyk.11 for ; Sun, 26 Sep 2010 13:19:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=d6rS9gKZGOLEguHSW7ag2MjEc5vm4LR3YDxLGnMY72Q=; b=nUFL5c6mmIrqR0Ngnsmxz22p57w8IBe6mKPN9ozgsBS1Mdad9FRbr6x0LuOqR4d14Y 21l4rkzAYlG8Lp/050tUmdnHzwQdWI/2Evh1ME3e2wG5JqmHqRtM0YuqXoaX3NLtxjgG i8xId8JcAYeGnx0Oesg2DXggm3u280FSb8xAo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=JZqNjgmXHlVWzrQaW86FTWEnjfECM0l3Nob90jKD59epHYFPRbrVMgR6CrjJ6eclIz +zLHUJrDbPqq632vCOKJmSveU+sTk+9hxSnzrnIT8IN3Cui10GPIP4a+dXsKqJ7MT29X UV/IZ3cUA07Of88JKDvx/sz19Gpts6n0/aWX0= Received: by 10.229.225.211 with SMTP id it19mr4878554qcb.87.1285532391572; Sun, 26 Sep 2010 13:19:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.15.65 with HTTP; Sun, 26 Sep 2010 13:19:31 -0700 (PDT) From: Andreas Veithen Date: Sun, 26 Sep 2010 22:19:31 +0200 Message-ID: Subject: [Axis2] Creation of the 1.6 branch To: java-dev Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org All, I'm going to create a branch for the 1.6 release (with the current HEAD of the trunk as the baseline). The first goal will be to determine if we need any releases from upstream projects. I'm aware that there are still ongoing discussions about what should and what should not go into the 1.6 release. This is not an issue because we can always change the baseline, i.e. remove changes from the 1.6 branch or merge additional changes from the trunk. In order to keep the branch manageable, I would like to propose the following guidelines (which proved effective for the 1.5.2 release): * Changes should not be done directly to the 1.6 branch. Instead, they should always be done to the trunk first and then merged to the branch if necessary. Of course, exceptions are made for release specific changes, e.g. changes required to make the branch compatible with releases from upstream projects. * Merges should only be done using a recent version of the svn command line client, or another client that updates the svn:mergeinfo properties. This is important to keep track of the changes that have been merged to the branch. Regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org