What does main/testing mean?

Tags: #<Tag:0x00007fc0bb280ea0> #<Tag:0x00007fc0bb280d60> #<Tag:0x00007fc0bb280c20>

When developer or QA person suggests user to try (usually for testing a fix or patch) a package in “main testing” repo what do they mean?

With the new Release Plan this is what they mean:

For a Release system the repo name is:

release-testing-znver1
or
release-testing-x86_64

For a Rock system:

rock-testing-znver1
or
rock-testing-x86_64

For a Rolling system:

rolling-testing-znver1
or
rolling-testing-x86_64

For Cooker:

If you don’t know and can’t figure this out you should not be using Cooker.

Ah, so now the clever user may wonder:

OK so what if the developer or that mean QA man says to use a package in “non-free testing” or “restricted testing” or “unsupported testing”? Now what?

Good question.

Append to the end of the name above accordingly:

-non-free

-restricted

or

-unsupported

Like using Rock x86_64 as example:

rock-testing-x86_64-non-free

rock-testing-x86_64-restricted

or

rock-testing-x86_64-unsupported

So now one might wonder:

Why doesn’t the naming system make more sense or seem more logical to users?

Good question. But I’m just a humble QA person not a developer. If you want that question answered you’ll need to ask a developer. Post-Edit: (Actually I think it mostly does make sense except that for the main repo the work main is no longer in the repo name.)