Bugday Wishlist

Bad example
Version bumps. A user who just copies to  does not save any time for us. Compare:


 * User:
 * 1) Copy  to  (10 seconds)
 * Developer:
 * 1) Review PR (10 minutes)
 * 2) Ask to fix the PR comments (20 minutes)
 * 3) Test the PR (20-120 minutes)
 * 4) Merge with comments and attributions (10 minutes)

Good example
A generic bug affecting many packages. It should not be too difficult to fix. Experienced users can support developers easily. The problem has typically an easy fix which does not require a lot of discussion or even changes in eclasses.

Suggestions
Enter your suggestion for the next Bugday here.


 * Testing pypy3 on more Python packages
 * Search old bug tickets and check, if it is solved already / still reproducible with latest version
 * Test, if programs which require CD/DVD/restricted downloads still install properly. (We have ebuilds, where no dev has the CD for. This topic requires users who have access to the media.)