| 1 |
Mart Raudsepp wrote: |
| 2 |
> Enabling tests by default feels like driving users away, because all of |
| 3 |
> a sudden their upgrades taken even more time (possibly unexplained to |
| 4 |
> them, as an EAPI bump in an ebuild introducing it is not visible to |
| 5 |
> them), and they'd just say to hell with it and go to a binary |
| 6 |
> distribution that runs the tests for maintainers only, as we should. |
| 7 |
> |
| 8 |
> Yet we have the _choice_ to take that extra time and double-check on |
| 9 |
> maintainers if they really did their job right. |
| 10 |
|
| 11 |
I agree that before EAPI 3 hits the tree we need to do some extensive |
| 12 |
pr. There should be a howto on the changes and what they mean to users, |
| 13 |
the benefits and costs etc. How to enable/disable those changes etc etc. |
| 14 |
|
| 15 |
But in reality all we need is 1 document, links and news items (yes more |
| 16 |
than 1 preferably) posted on our homepage, forums, mailing lists. Hell |
| 17 |
even within ebuilds if it comes to that. If after all that a user still |
| 18 |
hasn't figured out that they need to go read that document are we really |
| 19 |
in a position where we can do anything else. |
Archives