And how fast is that? I didn’t know there is a predefined speed for this kind of thing.
Scrivener is awesome. The current beta is awesome.
Scrivener is also very reasonably priced. I bought it years ago, and it’s still serving me wonderfully. (I didn’t say “perfectly,” but then what software clears that unreachable bar?)
I’ve got no idea why the release date continues to recede into the future. I don’t think I really need to know. And, I’m very appreciative of the program, of the work that’s gone into it, and of the dedication of the people who have created it.
As someone mentioned in another response, a middle ground exists between radio silence and daily updates. Nature abhors a vacuum and so do people. I saw a video from Hank Green about his work process - specifically, what is good enough to be “done” to him, which is 80%. No one reaches 100%, as perfection is simply impossible, and he knows that reviewing what is “done” may make whatever it is get to some point between 80% and perfect, but perfect will never be met. So it’s really like Zeno’s paradox in that way, and at some point he has to let it go.
Before the usual people swoop in, I am not suggesting that L&L just leave off at 80%. Maybe their “done” is 90%. Maybe it’s 75%. That isn’t the point. The point is that there is a “done” there somewhere where you have to kick the bird out of the nest. I hope that their “done” arrives sooner than later, whatever percentage it might be.
I don’t think periodic “we’re working it” updates are a terrible thing. Yes, there will be people complaining (as in another response further along than yours) that it shouldn’t take x time to build a piece of software. I don’t believe that. What I do believe is that going dark completely on the subject just lends itself to be used as fuel, especially when people get dogpiled for voicing their frustration, which in turn just leads them to become even more irritated. There is no upside in this scenario.
Your last update on the blog for WinV3 was almost a year ago. I think that’s simply too long a period without updates, and going forward, I hope you reconsider the time gap between them. Thank you.
11 pages!
The original question was answered on page 1 and continues to be answered to be answered with every RC release.
What follows is (apart from a couple of updates from L&L team) 10 pages of largely complaints and insults from both sides.
I’m not going to get into the argument on either side but IMHO largely a waste of brain cells and electrons.
Oh for a return to snail mail where everyone would have considered the waste of paper, ink and postage plus the week long delay before one’s opinion arrived at the chosen target, being glanced at then used to light the kindling or in this Covid era, toilet paper, avoiding a trip out into the bug filled world 
Back to my typewriter to work on my next masterpiece.
Because no matter what company it is, people will complain. A company should expect that. Having worked in the hospitality industry for over 20 years, I know the adage that "the customer is always right’ is BS. The customer is not always right, but to not allow them to air their frustration and receive some type of polite response is far worse than no response at all.
Whether you and I believe there should be no expectation is irrelevant.
In all fairness that’s our mea culpa. With Scrivener 3 on macOS we said Windows users could expect Win3 to be out in 2018. Then our Windows developer was sure it would be ready for mid-2019. And here we are, still working towards the release. In retrospect, what we should have said was that we were working on it and had no idea whether it would take another six months or five years. Had we done so, users would have had every right to be unhappy that it was taking so long, but no right to say that it should be faster. As it is, for the most part - excepting the very few users who are outright rude - we have only ourselves to blame for the frustrations of Windows users. Would that it weren’t so. The question is, how do we change internally to avoid these problems in the future? (That’s rhetorical, by the way. 
We have a pretty good idea of a number of issues we need to address; working out how is the bigger problem.)
I am afraid I have to disagree with you on this one, KB. I’m in IT. I see every day how people hear what they want to hear and ignore all cautions and caveats. Yes, it is something you could have done better – and I have faith in your ability to restructure the process to do so in the future – but it doesn’t change the fact that there is literally no way that you could have worded things more carefully that folks wouldn’t have found to crucify you for not meeting their own expectations.
The one option that could have work was absolute silence. NDA for all users/tech support that have access. Then only announce it when you are clear on delivery date. But then you’d still have the same questions “have you abandoned Scrivener for windows?”
There’s a worldwide plague of pessimists. To burgle a good line from George Bernard Shaw, “A pessimist thinks everybody is as nasty as himself, and hates them for it.”
I can see why some places use closed betas and NDA’s for everything, including bathroom breaks.
OK, for those people who can’t grasp this in context: the last update on WinV3 BEFORE THIS ONE was almost a year ago.
Thanks!
My post was intended for information, I read yours as having missed the update.
With the caveat that I’m happy with v1.9 & I understand development takes as long as it takes & L&L is (understandably, can’t make everyone happy etc.) conservative in whether to give estimates/updates, etc.,
Is the official estimate of v3 delivery in 2020 still good (say, 80% chance)?
Thanks.
Unfortunately, unless the whole planet is prepared to accept your stipulation also applies to them, I’d be surprised if this was sufficient incentive for LL to officially confirm any delivery estimate.
My suggestion is that you look at the logs / reports for the latest Release Candidate in the beta forum and make your own judgement.
I’m just using 1.9 and workarounds in other programs and online formatting services to get my job done. I’m not going to fool around with betas, don’t need the hassle. At this point, I’m not sure I’ll trust the initial release of v3 enough to risk my work on it. Seems like a confused mess.
That problem is not unique to IT. I worked retail for years and it was something I ran into on pretty much a daily basis. 