With the release of a June CTP of Team System you may be wondering, “Is the June CTP for me?” Here are my thoughts on that.

Yes

• If you just want to see what’s new since Beta 2. The June CTP represents 3.5 months of additional work since Beta 2 was locked-down back in February.
• If CTP is an acceptable quality level. This is a CTP release. As I noted in this blog post (Team System Community Technology Previews), CTP releases don’t undergo the same level of scrutiny as a beta release.
• If you want to see if a defect you reported in Beta 2 was fixed. If you submitted feedback through the MSDN Product Feedback Center, there’s a chance that it might be fixed in this release.
• If you want the latest documentation. The docs in the June CTP represent more than 4 months of additional work since the Beta 2 docs were locked-down.
• If you don’t mind a dual-server installation. This CTP will only support a dual-server deployment of Team Foundation Server.

No

• If you want to run production code on using the Go-Live License. CTP releases do not support running production code using the Go-Live License that was provided for Beta 2.
• If you have Beta 2 up and running already. You probably invested valuable time getting Beta 2 installed. Unless you have plenty of hardware, or you’re using VPCs, you should probably wait.
• If Beta is your minimum quality level. As noted above, CTPs are not as stable or reliable as Beta releases.
• If you find installation to be too challenging. The Team Foundation Installation Guide was not updated for this release. As such, you’ll need to discover what works on your own.
• If you prefer a single-server installation. As noted above, this CTP will only support a dual-server deployment of Team Foundation Server.
• If you're evaluating DSL Tools. The current DSL Tools release works with the Beta 2 version of Visual Studio.

Original Link