Yeah, that wiki entry is kind of old, even though it does express what remains an abstract philosophy to date. Basically, a lot of people buy active software on the premise that if they badger the developer enough they'll get whatever features they want---or they get attached to some notion that they feel the software really ought to do, and then feel ripped off it is doesn't come to fruition. So basically, don't expect *that* kind of development, where every feature request gets jammed in somewhere, and buying a licence entitles one to "vote" for features. So basically, don't buy Scrivener if it doesn't do something you really need.
The overall strategy of the application is maintained by one person, Keith Blount. He and I will discuss things to death. Every menu label and pixel in the interface is debated over, and we then test things back and forth for about a month or so before releasing changes to public beta, which bounces around users and gathers feedback, and finally becomes a part of the program officially. To see what all a typical release of Scrivener looks like, I'd point you to:
http://www.literatureandlatte.com/scrivChangeList.php
And I'd also point out that this is only last year's development, which started with a 2.x release so mammoth that there never even was a proper change log assembled. Best we've got is the "What's New" chapter (ahem) in the user manual. And at the bottom of that page you'll find a link to a whole different page that extends all the way back to initial release. Yup, that same initial release that promised to be the end of active development in the wiki, nearly five years ago.
Obviously, plans change. Back then Scrivener was one part-time teacher's hobby. Today it pays for several full-time salaries, including Keith who is now an ex-teacher, and a few part-timers as well. And we all love what we do and why we are doing it. By no means a big operation, but compared to your average shareware out there, it's got an actual team of people that are supporting it, designing it, documenting it, coding it, and continuing to keep it viable and modernised going forward. That team expanded for Windows, and may continue to do so for other platforms in the future.
So, sorry about the miscommunication on the wiki. Even though we do spend all day working on this thing, there are always 50 things on my list every day that don't get done for every 1 thing I do. Keeping up the wiki has been one of those 50 for a while too long I fear.
But for you, having Scrivener fall by the wayside is not something I think you have to fear.
--
Ioa Petra'ka
Scrivener - Outline. Edit. Storyboard. Write.
http://www.literatureandlatte.com/