[ckan-dev] Implementing UI changes to CKAN

[David Read]

> 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).

So this isn't a "really useful update" any more...? ;-)

> To keep it very simple: I'd recommend Richard just update to head on
> default and then do:
>
> hg branch feature-{ticketnum}-uireview

I prefer your previous naming policy - isn't that the one agreed? It
would be useful to have the policy in a wiki with the other developer
policies.

D