Warning: the term 'release' is a bit overloaded in this description. :)

A Release (in its most general sense, not how it is defined in OD), may contain many applications, each with a specific version to be deployed during a given window to an environment.

So, you would have something like this for any given release window:
- Application A - v1.1
- Applicatoin B - v2.1
- WebService Z - v1.2

Currently the concept of an OD release is at the application layer and I would have to track externally the connection between applications and/or versions.

So, what I'm looking for is a way to define an OD 'Meta-Release' that may contain many releases (you were warned) from one or more jobs within OD (one release per OD job).

I would then be able to define my November 2016 'Meta-Release' as being a culmination of the latest releases of each of my apps (above) that has passed QA (as defined in my Lifecycle).

Effectively this SHOULD give me a single button to deploy the given versions of the applications simultaneously so there is no chance something will be missed once reaching that point.

I know this whole concept of a monolithic release is somewhat archaic and no longer chic in the software delivery world. In an ideal situation this wouldn't be necessary as everyone would be using well defined continuous delivery methodology. But, snap back to reality and we find that many organizations definitely still use the idea of schedule release windows. My organization (and I'd wager many others) would definitely benefit from this kind of feature.