I'm usually pretty patient about this sort of thing, but I'm getting frustrated with Rise. The updates merely say, "we are almost finished with...." or "we are in the middle of...." An update gives expected dates of completion and details. We should see some movement to justify the project.
It's a two-edged sword. People want frequent updates, but the result of this is that it's often going to be a report of ongoing progress of some of the same things that were reported in the update before, simply because the things the team is working on require more than just a few weeks. More frequent updates doesn't cause development to magically be accelerated. It still takes time to develop something that functions well, is robust, feature rich, secure, stable, scalable. Rushing developments prematurely to market without extensive auditing doesn't do anyone favors either.
Expect audit reports to be released on Code and Web security in the next 2 weeks.
When you give update, you should put dates or percentage of what's done. And also people are looking for results, not just like "almost finished" or "in the middele of" or "a few more test cases". How few is that few - just 1 more or 50 more - and when do you expect to finish it?