[Helix-client-dev] Re: [Android-port-dev] a question on checking in code

All changes that are made on a branch should *always* go into the HEAD
and active parent branches (e.g. atlas-3.6.3 is a child of atlas-3.1.0,
so all changes to 363 are to be checked into the head and 310).

Thanks,
Jamie

On 9/27/2010 12:36 PM, Renjie Huang wrote:
> Hi all
>
> The current policy of checking in code is a bit confusing. It is not
> clear which branches we should apply the patch when fixing a bug or
> add a new feature.  According to Jim and Sheldon, the goal of  helix
> client will maintain only one branch 310,  and branch off when we are
> approaching product release and need stability. Can we make it a rule
> that all patches should be apply to HEAD and 310 branch? Thanks.
> _______________________________________________ Android-port-dev
> mailing list [email protected]
> http://lists.helixcommunity.org/mailman/listinfo/android-port-dev