Testing new releases on similar devices

Currently, we have this in our timeline:

Devices that were not tested need to be dropped

But, as for me, it does not always makes sense.

For example, imagine a situation that we have next devices in community category:

• google-peach-pit;
• google-peach-pi.

The only differences between them are:

• CPU frequency - only values are different, driver is the same;
• screen size - only timings are different, driver is the same.

Testing one of them covers 95+% of hardware of another.

I would like to move to community both of them, but I have only one to perform testing. If we require testing both, the second one will not be moved to community without an additional person having a device and wasting time on it

This raises a question, whether we really have to test all the devices or not.

Instead of testing 40 devices, I suggest to have such a list of devices to test:

• google-snow device;
• google-peach devices;
• google-nyan devices;
• google-veyron devices with broadcom WiFi/BT;
• google-veyron devices with marvell WiFi/BT;
• rk3399 chromebook tablets;
• rk3399 chromebook laptops;
• mt8173 chromebooks;
• mt8183 chromebooks.

This will allow to test only 9 devices, but cover 90+% of hardware of ~40 devices.