One big question for everyone: should we aim to have a bugfix release 0.5.0.1 or not?
I think we should have one if we can get some of the big crashes, as well as balancing problems fixed in the next few weeks.
We can also include any new features that happened to get done before that.
Anyway for 0.5.1 these are the things I’d like to work on:
- Saving, this is probably going to take a lot of my time, but will be worth it to finally have saving properly
- Making automated devbuilds again, so that it is much easier to ask other developers to test your changes as well as entice more patrons as there’ll be many more devbuilds to play
- Improving our CI to have additional code style checks and checks for unused variables.
- And then of course some bug fixing, but I’m feeling pretty burned out by churning out endless fixes, so I may have to stay away from bug fixing for a while to recharge.
So basically that’s probably at least a month if not two of work for me (considering that I’ll work full time next month before I take time off during the summer). I’ve been putting way more time into thrive in the past two months that I can in the near future.
Much Of the GUI should be editable without touching any of the code. There are some places in the code that use hard coded paths, but many of the places use NodePaths which automatically update when you edit the nodes in Godot.
Seems like many people have finals ATM. Maybe that means that we can’t make a quick fix release?
For now I’ll close the 0.5.0 milestone and move the remaining issues to 0.5.1 milestone. I’ll also dump some of the bug fixing issues there. These can be changed later.
And yeah let’s get this discussion going. Let’s not be too ambitious otherwise we’ll just need to cut features from the release once we reach the approximate date when we should release.