[ckan-dev] Implementing UI changes to CKAN

[Richard Pope]

On Thu, Dec 2, 2010 at 12:26 PM, Rufus Pollock <rufus.pollock at okfn.org> wrote:
> On 2 December 2010 12:18, David Read <david.read at okfn.org> wrote:
>> Richard,
>>
>> No probs. The branching policy is new, and James tells me we've agreed
>> to do it, so that'll be new for all of us.
>>
>> Basic setup of CKAN on your computer:
>> http://knowledgeforge.net/ckan/doc/ckan/README.html#developer-installation
>>
>> You want to pull/push by default all latest branches, so use
>> pip-requirements.txt
>>
>> BUT James said today that we should do feature branches from a stable
>> branch. So I suggest branching from metastable: 'Update clean' to
>> metastable (-C wipes any pending changes, but allows you to cross
>> branches): hg up -C metastable
>
> I don't think this is a good idea and this was a new policy just
> discussed today. I'm not clear why you'd branch off stable rather than
> default (with the new policy default should be pretty reliable and
> pushes to stable only happen at release time).
>
> To keep it very simple: I'd recommend Richard just update to head on
> default and then do:
>
> hg branch feature-{ticketnum}-uireview
>
> (There is a ticket right :) ?)

That was my 3rd question ;)

One per feature?


>
> Rufus
>



-- 
/*
richard at memespring.co.uk
memespring.co.uk
++44 7976730458
memespring (flickr/skype/etc)
memspr (aim)
*/