Devs: If you release a plugin with obfuscated/encoded files, it is *not* GPL compliant and must not be called GPL.

As the title says, calling your demo plugin the "GPL version" but then obfuscating and encoding crucial aspects of the code takes it completely out of GPL compliance. Every version of the GPL (and even the Apache license) states that

The source code for a work means the preferred form of the work for making modifications to it.

Everyone knows that obfuscation and encoding are done precisely to prevent making modifications to that part of the code. And the FSF has this to say about obfuscation:

Obfuscated “source code” is not real source code and does not count as source code.

If you would like to keep calling your plugin the "GPL" version, you must release the plain-text source of those obfuscated/encoded parts.