On 01/08/2014 09:53 PM, Lucas Meneghel Rodrigues wrote:
>  Repository Split Proposal
>  =========================
> 
>  Test Providers
>  --------------
> 
>  After a lot of discussion on how virt-test could be split in different
>  repositories, to fullfill the following requirements:
> 
>   * Make it possible for other organizations to maintain test repositories,
>     in other arbitrary git repositories
>   * Stabilize API and enforce separation of core virt-test functionality
>     and tests
> 
>  We came up with an idea called test providers: A loadable module mechanism
>  inside virt-test that can pull a directory that will provide tests, config
>  files and any dependencies.
> 
>  Test Provider Layout
>  --------------------
> 
>  .
>  |-- cfg      - Main test config directory. Holds base files for the
> test runner
>  |-- deps     - Auxiliary files such as ELF files, Windows executables,
> images
>  `-- tests    - Holds tests python files
>      `-- cfg  - Test configuration
> 
>  In fact, virt-test libraries are smart enough to support arbitrary
> organization
>  of python and config files inside the 'tests' directory.

Thanks for this RFC, it answers a lot of questions I had!  I took a look
through https://github.com/lmr/virt-test-experimental and found answers
to the other questions I had, bonus!

I remember before when repos. got split and re-organized, I had a lot of
(non-specific) trouble between my local repositories, copes on github,
and the upstream repos.  It was a while ago, but IIRC migrating my local
and my github repos, and handling pull requests were the major pain points.

Maybe a set of pre and post PR freeze is in order, to give people a
chance to tie up loose ends before PRs come flooding back in?

Also, docs (uggg) still need to be updated from the first repo split.  I
have most of those updates done, but they're not formatted or pushed
upstream.  However, this is necessary (and becoming more urgent) work.
IMHO, this should be added to the Schedule since it's unlikely to make
the 30-day deadline.  Otherwise/unless you have other ideas for this area?

-- 
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

Reply via email to