On Tue, Jul 19, 2016 at 11:11 AM, Cory Johns <[email protected]> wrote: > Roman, > > Can you explain a bit more about the Bigtop branch workflow? We certainly > want to make sure we follow the best practices to make reviewing our > proposals as easy as possible, and we realize that introducing a new tool > (Juju) adds a barrier as it is.
What I meant is to create a dedicated branch for you where you will put all of your current code and will keep refactoring it until it is ready for review and inclusion in Bigtop. That way, I can always check the entire branch when I do the review instead of guessing the context of various patches. Here's a silly example that still tripped me up quite a bit: I didn't realize that Charms on JIRAs require a Bigtop layer to be self-contained. Stuff like that. Thanks, Roman.
