Just saw this up on JavaBlogs.
The scary thing is the number of people who check in code at Level 1 
….
The next scary bit is how easy it is to think that you have something at a level 5, when really it didn’t reach two….
How do you go about improving that.
I guess the XP answer is continuous integration with a really awesome build server.
Anyone got good answers?
No related posts.
How can you verifiy any of the other levels w/out checking in code? ftp it to some other environment and run it and test it? That is the dark ages. With a good build environment, there should be no difference in #1 and #2. At that point most differences between #1 and #2 is in not adding/checking in every file that is needed. That is a human error not solved by technology. Nightly builds point out the human error. Emails to the group keep it from happening again.
Also, those orderings aren’t exactly ordinal. Something can work exactly correctly on your machine, but if you forget to commit or add a needed file, it won’t even compile elsewhere.
And just getting engineers to compile code before committing can be difficult.
Problems like this cannot be magically solved by technology. Problems of the build breaking are 99% problems of communication. No technnology can force you to have good communication.