arkady_kanev...@dell.com (arkady_kanev...@dell.com) wrote: > Adam and Vincent, > I fully understand and appreciate your suggestion. > > The real question is how to handle major code refactoring that affects all > barclamps (in this case OS ones). > Testing of refactoring takes a long time (multiple days). Every time a change > happens to any barclamp the long poll testing needs to be restarted. > > I am aware of 3 ways to proceed. > One, is to be able to break refactoring into smaller pieces. (This is what we > tried to do with database barclamp refactoring. But we were not successful > with running both database and MySQL barclamps concurrently.) That would > allow all work to proceed without blocking. > Second, to complete refactoring testing without changing any barclamps under > it. > Third, to merge it as is and fix consequential breakage. > > I am completely open to any suggestion, except for repeated testing of > database refactoring for any change in OS barclamps.
I still don't understand why there would *ever* be a need to block, if we use topic branches. However, now that steps 1--3 are done I guess we don't need to worry too much about this right now. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
