3 ms·

I wish people wouldn't do this. It makes it very confusing to know when it makes sense to upgrade, and depending on your luck you'd be getting a version that ha

I wish people wouldn't do this. It makes it very confusing to know when it makes sense to upgrade, and depending on your luck you'd be getting a version that has a bug fixed in the commit right after, but you wouldn't know because nobody announced a patch release. I get that release engineering adds a lot of overhead but it helps build a lot of trust between the developer and the user.

eslaught 3y ago
LuaJIT is in a very weird place overall. Some years ago, the main developer announced that they were stepping down. A bunch of forks sprang up as a result. Meanwhile, the main developer declined to put anyone else in charge of the project, and basically kept developing it on their own (albeit at a slower pace). The forks eventually died; no one was able to build enough momentum to keep a community going. So this policy was basically where we were anyway. I'm glad the project hasn't died, and in my practical usage it's been very stable, so I haven't had trouble grabbing random development commits off the Git repo. My impression was the release process was very high overhead, and I'd rather that the main developer stick around to work on the code rather than leave due to burning out.