Yes, yes.. We've all heard this already, but it doesn't excuse the lack of content in 1.5.2 IMO. When they push 1.5.2 to main branch it will seem similarly lacking at that point. Regardless of your development cycle, to create a new version (1.5.2) it should have a certain amount of content. There are also plenty of things I don't like about 1.5.1, and pushing this to main branch doesn't deserve a lacking beta version IMO. So perhaps it is a difference of opinion, but my company has never done anything like that with our software (make a lacking version just to push out an earlier version). If we had the same type of cycle, I feel like we'd delay the release of 1.5.2 despite pushing 1.5.1 and wait until a beta version could be offered that is not lacking.