Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of chris.custine@gmail.com
 designates 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=Bm2nN012rucAwHADCZjDsN5NyIn2z33grze9B0octteU7bPra2cikhKIF2GHHGjd7Hmf1+uTu4/s5GBCADBOz6/HeDU3JG5cUSyzIl4G3LRllDKSe7N24lO5hKpMd5ZcgwjqWwDx+FqlZDP20Q2KYxRb0EIGObdcX6XlV5UejSk=
Message-ID: <43b026c70612171803u7c9dafday479deae4cf6e7658@mail.gmail.com>
Date: Sun, 17 Dec 2006 21:03:48 -0500
From: "Chris Custine" <chris.custine@gmail.com>
To: felix-dev@incubator.apache.org
Subject: Re: Branch or not?
In-Reply-To: <a6cffa66b021ab01f41bace376b0d278@ungoverned.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7230_2321694.1166407428543"
References: <a6cffa66b021ab01f41bace376b0d278@ungoverned.org>

------=_Part_7230_2321694.1166407428543
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Not sure who you were looking for input from, but as someone who is working
with Felix daily I would definitely vote for a branch of the current trunk.
I think you do most of the commits to the core codebase anyway so I would
think a merge back down to trunk later on should be fairly straight forward.

Chris

On 12/17/06, Richard S. Hall <heavy@ungoverned.org> wrote:
>
> 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
>
>

------=_Part_7230_2321694.1166407428543--