CDI 2.0.1 does NOT exist, it is a binary version, not a spec fix so it looks ackward, nothing more.

All I am saying is that all CDI TCK release in the 2.0.x line correspond (or are aligned with) CDI API 2.0 release. There can be n releases of TCK for 1 release of spec. Though there are limitations on what a TCK release for an already released CDI version can contain. This should be captured in docs inside the TCK.

That's how it worked under jboss at least. It is eclipse project now, so the process might differ.

Also, what Martin pointed out pretty much settles the discussion. The ordering is given by the spec after all.