I would add my voice to the chorus as well -- yes netplan looks like a very good step forward, and yes it is immature (see e.g. https://ubuntuforums.org/showthread.php?t=2391351) and thus you _should_ have made it optional.
Also, netplan usage reference is very good -- but for an immature project that may have (and in fact does have) bugs, some "under-the-hood" admin/developer/hacker's overview would be essential; instead, your "troubleshooting" page assumes user's fault and correct code, which is not necessarily the case.
So since essentially an LTS system update may all of a sudden break all your networking, may be putting some simple instructions on how to chop netplan off the system on your netplan.io page would a little to avoid all this stress and confusion.
@cyphermox
I would add my voice to the chorus as well -- yes netplan looks like a very good step forward, and yes it is immature (see e.g. https:/ /ubuntuforums. org/showthread. php?t=2391351) and thus you _should_ have made it optional.
Also, netplan usage reference is very good -- but for an immature project that may have (and in fact does have) bugs, some "under-the-hood" admin/developer /hacker' s overview would be essential; instead, your "troubleshooting" page assumes user's fault and correct code, which is not necessarily the case.
So since essentially an LTS system update may all of a sudden break all your networking, may be putting some simple instructions on how to chop netplan off the system on your netplan.io page would a little to avoid all this stress and confusion.
Thank you.