Return-Path: Delivered-To: apmail-incubator-felix-dev-archive@www.apache.org Received: (qmail 29450 invoked from network); 18 Dec 2006 01:51:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Dec 2006 01:51:39 -0000 Received: (qmail 46518 invoked by uid 500); 18 Dec 2006 01:51:46 -0000 Delivered-To: apmail-incubator-felix-dev-archive@incubator.apache.org Received: (qmail 46349 invoked by uid 500); 18 Dec 2006 01:51:46 -0000 Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: felix-dev@incubator.apache.org Delivered-To: mailing list felix-dev@incubator.apache.org Received: (qmail 46338 invoked by uid 99); 18 Dec 2006 01:51:46 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Dec 2006 17:51:46 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [217.160.230.40] (HELO mout.perfora.net) (217.160.230.40) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Dec 2006 17:51:36 -0800 Received: from [75.21.184.140] (helo=[10.0.1.3]) by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis), id 0MKp2t-1Gw7es0Pab-0000FR; Sun, 17 Dec 2006 20:51:15 -0500 Mime-Version: 1.0 (Apple Message framework v624) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: felix-dev@incubator.apache.org From: Richard S. Hall Subject: Branch or not? Date: Sun, 17 Dec 2006 20:42:14 -0500 X-Mailer: Apple Mail (2.624) X-Provags-ID: perfora.net abuse@perfora.net login:b399c17105f59dfa36985f08f30e623d X-Virus-Checked: Checked by ClamAV on apache.org I want to start implementing the require-bundle function for Felix, but I wanted to get some advice on how to proceed. I did my initial prototyping in my sandbox and I will use that prototype as the basis of the new work, but won't merge it back into the trunk since it is way out of sync with the 0.8.0 release (and it a little hacked). So, the question is, should I make another branch of the trunk in my sandbox or should I do it directly in the trunk? I am leaning toward making another branch and merging it back in when finished, since I imagine that there will be some intermediate commits that will break some things. Does everyone agree that this is the best way to go? -> richard