Forena 7.x-4.0 Release

David, I'd also vote for the "assign parent issues" approach, for the same reason as you mentioned. However can you provide some extra details about the "we assign" part of it? In my opinion there are 2 approaches:

1. You assign them, so that forena users know what you consider as release blockers.
2. Anybody can assign them, and you then decide if such issue is indeed to be considered as a release blocker. If you disagree, you update such issue accordingly.

Maybe combine both approaches, whereas you have the final word if needed?

Just slightly refined the issue description, to reflect the approach we've been using now for a few days, and which I think works great! With that I think it also reflects the choice for option "2." I mentioned in comment #3.

1 more related thought: to avoid the list of child links to get too long, it appears to me that we should consider removing the parent link again when a child issues received status fixed. Or maybe only when it becomes closed? Doing so we might consider "an empty list of child issues" as the milestone to start thinking of a 7.x-4.0-rc1 version (for which I think we're getting close already). If we don't want to remove those parent links, a list of child issues in status fixed (or closed) would be the alternative for such milestone.

David, as of right now it is not an all green list yet. But note that there are, in my opinion, no more issues to be added to this list, while I completed a few more (new) issues I wanted you to consider for inclusion also. The only issues that aren't green yet, are yellow ...

I look forward to soon turning the remaining ones from yellow to green soon ...

David, I removed #2355193: Extend community docu as a release blocker, and added a few more details in my #10 comment there about what remains to be done for that issue. Your feedback on what to do with the info about available videos would be appreciated (one of the few remaining things that stops me from considering that issue as fixed also).

With that we only have 1 yellow release blocker right now!

David, you're "Le Patron", aka the boss of forena. So I think because of all the effort that you put in this amazing new release, you should have the honor of hitting the magic 7-x-4.0 forena button. But just to make you doubt a very little bit, keep in mind that the forena project page contains enterprise reporting. In the enterprise world where I originate from, it's common however to have like a 1 or 2 weeks FROZEN period. If you want to consider that, then I think you should consider a rc1 version.

To compare it to the upcoming D8: the very first D8-beta1 release was assumed to become available after about 10 days of "no new critical bugs" showing up anymore. But the night before that D8-beta1 became available (at DrupalCon Amsterdam) there was a brand new issue that was considered such critical bug. But for some reason (to not ruin the Amsterdam party?) some people jumped on fixing that bug, so that before the end of DrupalCon Amsterdam D8-beta1 was released anyway. All this just to illustrate what "I" would do if I was you: let's go for 4.0 N.O.W., and if anybody does find a 4.0 showstopper in the very near future, I'm confident that we"ll get it fixed soon, so that you can come up with a 4.1 whenever that makes sense.

PS: "revert reports to original" still contains a typo (= originla or something), haven"t had a change to fix that very last tiny thing that bothers me in the nearly-to-be-4.0. Maybe you want to consider that as a last minute change for you to apply (which doesn't seem to require "testing" ...)

+1 from Belgium for David's final GGGGGOOOOO !!!

Yes, forena 7.x-4.0 has arrived!!! It makes me think of Le Beaujolais Nouveau, which is about to be released also (typically on the 3rd Thursday of November).

Thank you too David for all your work in this (and all prior) forena releases, not to forget your responsiveness about all the forena support requests. Hopefully my docu contributions will help to reduce the amount of such requests a little bit.

Now that this issue has been marked as fixed, I'm looking forward to the creation of an issue with a title like Forena 8.x-1.0 Release ... or maybe 8.x-5.0 ?

Note: most of my work on documentation and testing was funded by In Petto.