Re: [gentoo-project] New gen-b0rk repository specifically for Q/A tools testing

[Brian Dolbec]

On Sun, 1 May 2016 16:53:16 -0700
Brian Dolbec <dolsen@g.o> wrote:

> In order to further improve the chances of Q/A tools catching
> errors.  I have created a new repo (overlay) which will contain
> minimal test case ebuilds.  The idea is to have test case ebuilds to
> run repoman code against.  The outcome of these runs should be
> comparable to pre-recorded output.  In that way as more code changes
> are applied as part of the stage3 re-write as well as new test cases
> and checks to be added to it's capabilities.  It should minimize the
> bugs introduced in releases.
>
> Repoman does have some unit tests, but it is far from 100% coverage.
> Also with the major structural changes that the code has been
> undergoing, it is not always possible for the unit tests to be
> compatible with the new code.
>
> This new repository is open to all Gentoo developers to contribute to.
> All we ask is that you follow some simple common sense rules for
> adding additional test ebuilds.
>
> The repo is located at:
>
> https://gitweb.gentoo.org/repo/proj/gen-b0rk.git/
>
> Here is the README included in the base directory.
>
> This repository is for the primary purpose of testing Q/A tools like
> repoman.
>
> The ebuilds it contains are for testing specific areas of tests that
> are performed as part of the normal operation of that Q/A tool.
>
> This repository is open to all Gentoo developers under the following
> rules:
>

<snip>...

> 7) New module development and test ebuilds will be done in a branch
> or personal repo and submitted to the gentoo-portage-dev email list
> for review and approval to merge into master.
>    NOTE: This rule is lifted for the initial creation and population
> of test ebuilds to use to test out the repoman code.  An anouncemnt to
>          the gentoo-project email list will be made when this initial
> population period is being ended.
>
> 8) Signed commits only, also signed-pushes are mandatory
>

Please note we are not restricting push access to the master branch yet,
we need a decent db of test ebuilds before we will lock it down more to
maintain some Q/A consistency.

So, push your test ebuilds you create without worry.

If you are unsure about some specifics and want it reviewed, then sure,
submit them for review and fine tuning.

Thank you

-- 
Brian Dolbec <dolsen>