> On Monday 17 March 2014 00:55:51 [email protected] wrote: > > Sascha, > > [snip] > > > We have > > nearly completed the migration of CB2 work to OCB include the > > OpenStack and Hadoop workloads. I think we just need to work out a > > migration plan that could leave CB1 work free to move to trunk. > > So from these two sentences I read that the plan is to indeed move > everything over to opencrowbar right?
Yes, we're moving all CB2 work (trunk of Crowbar) to OCB > > Reducing cross-code base > > confusion was part of the rationale for splitting CB1 and CB2 work. > > While I haven't been part of these discussions, I appreciate whatever > simplification we get. And I guess it obviously needs a transition > period for the technical aspects to be solved. On the other hand, I am > wondering about how we're to organize our neat little community here. > I assume both groups will continue to share this mailinglist, right? That was my hope. There's not so much traffic that it's confusing and I believe there is a crossover. So, yes. One mailing list. > > I > > share/understand your feelings about DevTool - we did not > > reimplement it in OCB. The challenge is that we (Dell) still need > > to be able to create old builds. So changes that risk legacy builds > > or require effort to test alternate builds would be difficult to support. > > Understood, but I guess at some point it's about either moving the > ./dev tool based repository layout to the new org or to re-implement > building old releases under the opencrowbar org. From a Crowbar-1 > contributor's perspective it would look a bit unfair to move only the > fancy parts to a fresh github org and leave the "legacy" bits in the > current one. Simply because this is severely slowing us down. So for > Crowbar-1 people, this is actually a good opportunity to address > long-standing concerns, such as reducing the number of branches per > repository and probably the amount of repositories itself, Travis-CI > and whatnot. > > > Suggestions? Rob I think there are many low-hanging fruit cleanup items that would be low risk. It's important for now that we can still build recent releases using DevTool. The plan we distributed in November was to get a fresh start since we felt there was regression risk in refactoring. If I had suggestions to fix it, I would have made them then. Moving to a new org was my 3rd choice and reluctantly done. > Others than a slightly ironic "get your ass off the turf fast, man" I > think we should make sure the community remains healthy :-) For the > technical challenges you face, I guess the answer is easy: You made > the decisions, you'll find the solution ;-) > > Thanks for sharing some more thoughts. > -- > Viele Grüße, > Sascha Peilicke Going with the turf analogy... I'm seeing great work on CB1 but, frankly, the grass is greener over in OCB. The designs are joint efforts with many of you (esp. Adam) and significant improvements (like RPM packaging, upstream cookbooks, simple git) were done specifically to address issues raised by your team.
_______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
