[ckan-dev] Another branching question

[David Read]

1.3.3 is still in beta, so all fixes should go onto that branch.

I guess if this wasn't the case then you could branch from 1.3.3 to
create 1.3.4. (i.e. rather than branching from default, as that would
pull in lots of unneeded new features as well, which would increase
risk for this immediate release)

David

On 1 April 2011 19:25, Seb Bacon <seb.bacon at okfn.org> wrote:
> Hi,
>
> I want to check in a trivial fix for a client
> (http://trac.ckan.org/ticket/1063).  They are currently on
> release-v1.3.3.
>
> Should I cut a new v1.3.4 release?  Or make a client-specific branch?
> If the latter, should I fork the repo, as it's probably not right to
> have branches for OKFN clients in the main CKAN repo?
>
> Any ideas?
>
> Seb
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>