On 11/18/2013 08:55 AM, Ademar de Souza Reis Jr. wrote: > the API and tools. To keep things working smoothly, we'll support > the current (stable) code-base and start working on a new one
Suggestion: * Fork what we have into an entirely new github project, e.g. "autotest1". * On the new project fork, take a heavy-handed hatchet and delete all parts (code) that don't fit the 'stable' and 'low change-rate' criteria. If in doubt, delete it. * Split up the repo and tree as proposed, splitting along 'module' and/or API lines into multiple git submodules. * For each submodule, re-built bottom-up, toward stated goal for the API/module. Copy-paste old code (with adjustments) and/or write new code. N/B: The theme here is, a parallel "top-down" and "bottom-up" approach. Use top-down methods to define high-level structure and prioritize module-level goals/targets. At the same time, use bottom-up coding within the structure to minimize re-work as (in parallel) changes happen. -- Chris Evich, RHCA, RHCE, RHCDS, RHCSS Quality Assurance Engineer e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214 _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
