Consider making a glad2 release / tag
After weighing the pros and cons of all of the alternatives out there, I've found that `glad2`, even in its beta state, is the only viable replacement for `libepoxy` in my own production library, [libplacebo](https://code.videolan.org/videolan/libplacebo). The upcoming libplacebo v5.288, slated for release sometime in the next week or two, will be the first major libplacebo release to depend on glad2 internally, currently in soft-bundled form via git submodule.

However, this is a bit awkward for distros, since libplacebo source tarballs do not contain bundled submodules, seeing as distros tend to be expected to package dependencies separately. However, it's a bit unfortunate that glad2 does not have a stable way of referring to it other than pinning some arbitrary git commit. I rather doubt most distros will be willing to package some random beta branch with no tag or version number.

Given that glad2 in its current state is, in my estimation, usable enough to be used in production code, I think it wouldn't be too far off the mark to consider just making a proper release that I can depend on. Or, failing this, what do you think urgently needs to be addressed before the first `2.0` tag?