Sorry - the original post had been spammed so I didn't see it until the second post.
Firstly, I'm really sorry about the radio silence. As Drew inferred in an earlier post I've not been involved in Perch (other than the fact I deal with the business admin and the servers) for some time. The product doesn't make enough money to justify two people working on it.
As things stand there is not active development happening with Perch. I believe there are issues with Shop and the SCA requirements, Shop has never had enough usage to really justify a lot of work to implement these things. When we launched it we hoped it would drive take-up of Runway but that hasn't really been the case, and making it a paid add-on would not have made a lot of difference. So I don't think developing that further is something that is likely to happen in the near term.
In terms of the core product, if there are compat issues with newer versions of PHP I'd be keen to find out what they are in order that people don't run into those, as that seems like something I could get fixed. The core products, Perch and Runway, are very stable and there is no reason why people shouldn't be using those for as long as they want a PHP based CMS, however things like Shop require constant changes to keep up with legislation, and that's not something I'm going to be able to invest time in. My suggestion is that we move those to GitHub under the same account as the docs (they currently live in a private git repo, so that should be easy enough to do) and then if members of the community wish to help fix those issues that's great.
I'll keep an eye on this thread now anyway if folk have comments but I feel that is probably the best course of action right now. I'm sorry I don't have better news of a new version, however given the current climate I feel the key thing is to make sure that things are stable for your sites.