Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> We want to solve those exact problems in CB2 but that creates a huge
> cleanup lift for CB1 that risks CB1 stability.
Sorry - we must have a major disconnect here because I can't
understand this at all. Please can you explain what you mean in more
detail?
> Adding fix CB1 to the work makes it unlikely to succeed.
I'm not proposing any kind of coupling between CB1 work and CB2 work.
In fact, I'm proposing exactly the opposite! Sever the remaining links
between the two, i.e.
- introduce branching to the main repo
- move any remaining release-specific docs from the wiki into
the relevant branches in the code repos
and then each release is free to proceed in any way it wants without
any risk of destabilising another release.
Once again, this is what branches were designed for. They worked fine
long before github organizations were invented.
> If you want that as an action item then the field is wide open.
SUSE has already done a lot of work on the CB1 barclamps. But we are
mostly paralysed when it comes to the main repo, because of the
above-mentioned lack of branches. That's a really frustrating
position to have been in for the last 12 months:
http://lists.us.dell.com/pipermail/crowbar/2012-November/001845.html
_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
