>> Ok, so the linking issues were simply me being silly. I forgot >> to run `make ragel` and commit the output (to use a git gem). >> Unicorn now run just fine under 3.0.0-dev (current master). > > Odd, just "make" (no args) should work.
It does, but the files it generates are in .gitignore, and I was trying to use the gem through bundler's git gems. Anyway, now I know the drill. > Anything else in the ruby 3.0 pipeline that might introduce > incompatibilities? Not that I know of. There not any big breaking change planned for 3.0. > Not sure if releasing unicorn 5.7 is worth doing soon/now or > closer to December 25... It is up to you. But the sooner the better for me. We run our master branch CI against ruby master on a nightly basis. Until this patch is released I'll have to keep a fork around.
