[ckan-dev] release branches, etc

[Rufus Pollock]

CKAN v1.3 is released so we can't patch it but knowing that we already
have some fixes David (R) and I on Friday created a release-v1.3.1
branch which contains the fix you want :)

(NB: naming convention going forward release-v... not ckan-....)

Rufus

On 28 February 2011 17:43, Seb Bacon <seb.bacon at gmail.com> wrote:
> Hi,
>
> I'm working on a client deployment (DataGM).  The currently
> checked-out branch on the live server is ckan-1.3; it used to be
> metastable.  Someone else set it up & I'm not sure what the
> best-practice here is.  In particular, there are some bugs recently
> fixed in various branches and I'm not entirely clear of the process
> whereby they get into release branches.
>
> Do we have a documented policy somewhere on this?  If I want to
> cherry-pick bugfixes to the ckan-1.3 release branch, what should I do
> / who should I ask / etc?
>
> As an example, I want this fix:
> https://bitbucket.org/okfn/ckan/changeset/1b8fedeb7ab0/
>
> Thanks
>
> Seb
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>



-- 
Co-Founder, Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/