Version Control Policy: Best Practices
Your code base is always under version control (if it's not, it's high time you did!), and developers are always scared about taking updates or committing files, under some supernatural fear, that an update will wipe out their local changes. This causes a lot of trouble in the team, when some developers have not updated their code base since a long time. I've compiled below a checklist of best practices. Before you check in your code to subversion, here are a few points to follow. Ensure that there are 0 (zero) serious CheckStyle, PMD, FindBugs error (warnings should be reviewed). If you need an exception Checked in Code must build with all dependencies (not just your module). Checked in Code must not break unit tests. Checkins without comments should be noted as a build break caused by the developer. Before committing your changes to repository, it is advisable to synchronize the files, run an update and then commit your changes.