Kian-Tat Lim Frossie Economou I'm getting back to this a little late... When you are discussing the TCT/SAT relationship at DMLT Nov2014, please review whether this Policy even needs TCT approval. The TCT is supposed to sanction every change to Official DM Software Releases (i.e., the 6 or 12 month Releases). This Issue discusses the addition of 'new' 3rd party software on which the Release does not depend – i.e. if it wasn't there, the Release would still build and could be used in Production if it passed all QA tests. Until that 3rd party software becomes a required artifact for a Release's build, it doesn't need TCT approval. It's up to the SAT to determine if a 3rd party software is acceptable for exploratory mode - which I would class as any optional dependency.
So wrt the TCT current mandate, this is not relevant. Once the TCT mandate is revised, you should revisit this issue keeping in mind the new mandate.
Regardless of outcome, this Policy statement should be added to https://confluence.lsstcorp.org/display/DM/DM+Third+Party+Software so the SQuaRE team has a summary of all TCT approved software allowed in an Official DM Software Release and all SAT approved optional/experimental software. (And it just was added there.)