Bigbug Potentially, but we've already removed the old cron setup from develop. Ideally, I wanted to give people a little more notice to change things.
JosephWithCOR The separate develop branch and release cycles are part of a wider initiative involving roadmapping, tracking bugs and features to ensure they get done, and overall stability. The develop branch has proven itself to be a great place to properly work on & test bigger features without impacting production installs. Maybe monthly is too long, but I think we'll find a middle-ground eventually.
Personally, I want ITFlow to be as rock solid as other apps people are using in production. The whole commit & push as you go didn't really provide that (see the tens of forum posts asking why X doesn't work even though there's a big banner over the top of it that says its in development).
You're perfectly welcome to use the develop branch if you want: update config.php
and do a git switch develop
. If it breaks: you get to keep both *pieces!