[ckan-dev] Implementing UI changes to CKAN

[Rufus Pollock]

On 2 December 2010 12:27, Richard Pope <richard at memespring.co.uk> wrote:
> 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?

IMO you can have a branch in which you do multiple tickets/features if
they are part of some overall 'big feature' -- but I sugges there
should then be a meta-ticket (in this case something entitle CKAN UI
Improvements Dec 2010 (to distinguish from Dec 2009 effort!) which you
can use as the ticket number.

Rufus