Comment 22 for bug 1061069

It seems CUPS introduced a chicken and egg issue:

If desktop toolkits use CUPS 1.6 APIs to get dynamic printers support
they need CUPS 1.6 installed on end-users machines but CUPS 1.6 cannot
be used on end-users machines until desktop toolkits use CUPS 1.6 APIs.

It seems one needs to do a "big jump" and upgrade both CUPS and the
desktop toolkits at the same time.

To prepare for such a "big jump" experienced users must test it
in advance before usual end-users get it.

To let users test it, I think we should have a new OBS project
whereto CUPS 1.6 and other related packages can be submitted
e.g. something like a "Printing:Playground" project to make
the distinction obvious that "Printing" is meant for (relatively)
stable stuff that can be used without expecting major issues
in "real-world environments" (e.g. on SLE11) but in contrast
"Printing:Playground" is meant for venturous testers who expect
even unexpected issues.