What's your preference? One (quite) long review publication, or a shorter one along with some discussions here?

Roadtests generally require some amount of software and hardware development in order to do the evaluation, so I find it helpful to document that as separate blogs posts.  I find those posts extremely useful in generating a more concise summary for the review itself.  If I tried to do it as one long review document, I would have difficulty editing it.

I was just thinking about this more.. technically it's harder to write concisely and strip off unnecessary content, so that's another reason, why shorter posts are more appealing.

I don't like it when there are excessive dumps of output that might better as a zip attachment (or a repo somewhere), because I feel the reviewer ought to look through the results and provide their analysis for the readers benefit.

Also, for some reason, I've never really liked that collection of photo feature (which slides images past). I think it's far easier to scan through a blog when it has normal image attachments than figuring out how to quickly click or slide through to the images of interest. But I know people use that feature so maybe I'm just not operating it correctly.

fully agree, blog posts and a RoadTest review to summarise.

Great point about getting reader feedbacks 

Hi,

If you're creating many separate posts, it's almost always far better to use 'blogs' to create them, rather than 'discussions'.

I've found it's almost always never worth using discussions unless it is a short question being asked, or just a link or other extremely small snippet of info being given. Discussions are very hard to find afterwards, whereas Google maybe searches out blogs better.

Maybe I'm wrong on this, but my experience has been I've always regretted discussions because the interesting topics end up being expanded a bit more or people will provide interesting information in the responses, and then it's hard to find afterwards when it's a discussion rather than a blog. 

I like the multiple shorter posts, organized chronologically like chapters of a book. As others have commented, a 5-10 minute read is better for getting thru the post without other distractions. 

When I publish shorter posts based on testing milestones, I feel more like Im making progress in the test. Those shorter posts also help me to find test gaps and mistakes as I go. 

I also prefer multiple shorter ones.

I prefer the all in one place review. But it depends. If there is a narrow topic or focus area within the review that warrants a deep dive then a separate blog post is certainly useful (kinda like an addendum).

I find multiple reports both easier to write and easier to read.

From the writing point of view -  I think it helps establish a dialogue with the audience and getting comments as you do the work helps steer it in  better directions.

From the reader's point of view - finding 5 or10  minutes to read a blog is not too hard - 30 minutes is more of a problem.

MK

I'm in exactly the same position, currently reviewing the CM5 module. Most of my previous reviews were published as one lengthy report, but this time I've decided to write a series of blog posts and wrap things up with a final RoadTest summary.

One advantage of this approach is that you can publish updates as you go, rather than having to wait until all the work is done. This means the results become available to the community much sooner, and you can also adapt the direction of your review based on feedback and responses to your earlier posts.