v20 roadmap

[RoboMWM]

Kanban board: https://github.com/orgs/GriefPrevention/projects/1/views/1

Everything on that board are brainstormed ideas. Ideas get finalized into future tasks in milestones.

[RoboMWM]

I've decided to simplify the roadmap. Would be nice to get to a round "v20," but at this point I'm looking more at making gradual changes. To get to more maintainability, things will have to be removed or moved eventually, and that will denote major release bumps.

I initially had ideas to refactor the configuration to be split into multiple files, but have decided against that as it may introduce needless complexity (and more files to paste for issues and troubleshooting).

[RoboMWM]

The project board is brainstormed ideas. Milestones will be used to be a more "finalized" version of what to expect. I will be cleaning up existing open milestones to reflect this.

[RoboMWM]

As per 9fd8b49#commitcomment-136630261 v17-v19 will be released only in beta channels on bukkitdev and modrinth. When v20 makes its way around, it'll be pushed as the release version along with associated warnings and converters.

[RoboMWM]

v16 will remain as the "release" version of GP until v20 is ready to be released.

v17+ is what will be pushed to users whenever possible (i.e. for fixing non-critical bugs, for wanting certain features removed, etc.)

[RoboMWM]

After v20 is released and made the official release version of GP, v16 will probably be semi-maintained (mostly by community) in a purely bugfix-only branch for those who wish to remain for the removed features or API, but will not be supported in any other capacity.

[RoboMWM]

Legacy branch exists if we ever want to reference the original Big_Scary logic for a rewrite.

Major refactors or straight up feature additions to master are the things that I'm currently putting on the backburner for master.

Major refactors to legacy branch will be rejected. New features are 'ok,' provided they are small and deemed 'easily maintainable.'