I’ve moved around a few things in the opening post list, in particular moving the planned but not started items for 0.3.2 to 0.3.3. The reproduction system overhaul is ahead of schedule too, so I moved that from 0.4.0 to 0.3.3.
I’ve seen a few people on Slack talking about releasing in the summer, and this worries me. Yeah, we probably would collectively have more free time then, but that hasn’t exactly helped in past summers. I think we should aim for April 30th at the absolute latest for 0.3.2. The two big features, compound clouds and a tutorial, have been effectively done for ages now, and we’re mostly waiting on performance improvements and some tidying of the CPA code (and sound effect things, but I have that covered…hopefully).
I’m even willing to say if the performance improvements remain in a half-finished state all the way up to the end of April, then we say screw it and push them to next release. I think it was @hessnake and @SpasticMelon who were working on that, and they’ve…uh…kind of disappeared, so I don’t see much hope of it being completed without us getting more programmers, which won’t happen until we do more outreach, which we’ve decided won’t happen until we complete 0.3.2. So basically, unless @moopli or @crovea get more time, we’re stuck in a catch-22. We could wait for that to happen, but in my opinion we can’t keep waiting too long. It’s what nearly killed the project between 0.2.4 and 0.3.0, and when we have the opportunity to do so much after the next release, we can’t afford to let that happen.