CC: @Co0sh, @joblo2213
I think once #1007 and #1006 are closed we can tag this as 1.11 and shift dev to 1.12-dev. What's the process of getting changes to spigot and updating the wiki? It'll provide some exposure to a new audience as well so possibly some more newcomers to discord/discussion thread as well.
It's not automatic. I'll have to compile the plugin and upload it to Spigot manually. The wiki is a git repo, so I'll just clone it locally, replace all the files with the contents of _/docs_ and push those changes.
Once I close those issues I'll create a v1.11 branch with appropriate config and tag you in.
Might see if we can squash #1004 in this release as well since @Wolf2323 has put a lot of work into getting that ready.
@bundabrg any updates?
Just recovering from pneumonia. Will be in touch.
I think we're pretty much ready. If #1030 is merged (and only you can do this one I'm afraid as it requires owner access to generate the keys) then it can be part of 1.11 as well and cherrypicked into this branch first. The release can then be tagged.
I'll have time tomorrow :+1:
Since the Spigot page is in my hand, this is not a problem anymore ;)
Most helpful comment
Might see if we can squash #1004 in this release as well since @Wolf2323 has put a lot of work into getting that ready.