So people are likely wanting an official (CurseForge) release for CC with all of the new features.

To encourage this, perhaps @dan200 should have a period of time (a month or two?) where the only pull requests which get merged will be the ones which fix bugs and improve stability/compatibility. Once a CurceForge version is out, the 'bug fix only mode' will be removed.

The hope here is that restricting feature pull requests will encourage those working on new content to also maintain the older parts of the mod.

I'd be glad if we got a new release at all at this point ¯\_(ツ)_/¯

Whilst there is some work which needs to be done on stability, I'm not sure if it needs a dedicated period quite yet. Most of the game-breaking bugs have PRs already, and the remaining ones either require serious diagnostics or community discussion. Personally, I feel if the aforementioned PRs are merged, we could get away with a beta, which is "good enough" now.

<off topic>
Honestly, I'd really like to see some love for some of the older PRs. I realise they are pretty hefty, and so require a lot of time to review, but it's also pretty dispiriting seeing stuff be neglected for 4 8 months.

There's a bit of me which wonders what Dan's thoughts would be on getting someone else to help manage some of the smaller PRs, so he can devote more time to the larger changes. It'd help ensure the small changes don't fill up the PR page, whilst not handing off creative control to someone else. That being said, I don't want to pressure Dan into anything as, after all, it is his mod.
</off topic>

Continuing the off topic bit, I know that several people, myself included, have thought of you (@SquidDev ) being a good candidate for the "Dan's helper position".

Honestly, I would just like a statement that a new release will be done by such and such date. It would be even better if dan could throw out a list of things he'd like the community to do before such a release. This could include things like:

• Eliminating merge conflicts between branches he wants to merge
• Updating the whatsnew, help, and other .txt files
• Verifying the stability of the build and fixing any remaining issue (though he'll probably do this himself)