Personally, I¹d still vote for feature branching: I¹d really love to see
an Angular Panels feature branch worked on separately and then merged back
in; effectively, Travis¹ 2nd option. Pick 3(?) panels, like Users, Images,
and the System Information one I¹ve seen around, iterate quickly, merge in
Hi Doug!
I think the is a great discussion topic and you summarize your points very
nicely!
I wish you’d responded to this thread, though:
https://openstack.nimeyo.com/58582/openstack-dev-horizon-patterns-for-angular-panels,
because it is talking about the same problem. This is option 3 I
I have two suggestions for handling both new panels and refactoring existing panels that I think could benefit us in the future:
1) When we are creating a panel that's a major refactor of an existing it should be a new separate panel, not a direct code replacement of the existing panel
2) New
