Don't apologize!

• Breaking the build once in a blue moon is not a big deal, and should never be a show-stopper.
• It's your manager's fault for not configuring continuous, automated builds.

Also, I bet your team fails the 'Joel Test' and can't make a build in one step.

If so, this would be another thing that you shouldn't apologize for. Indeed, it's a team anti-pattern.

Don't apologize!

• Breaking the build once in a blue moon is not a big deal, and should never be a show-stopper.
• It's your manager's fault for not configuring continuous, automated builds.

Also, I bet your team fails the 'Joel Test' and can't make a build in one step.

If so, this would be another thing that you shouldn't apologize for. Indeed, it's a team anti-pattern.

Don't apologize!

• Breaking the build once in a blue moon is not a big deal, and should never be a show-stopper.
• It's your manager's fault for not configuring continuous, automated builds.

Also, I bet your team fails the 'Joel Test' and can't make a build in one step.

Don't apologize!

• Breaking the build once in a blue moon is not a big deal, and should never be a show-stopper.
• It's your manager's fault for not configuring continuous, automated builds.

Also, I bet your team fails the 'Joel Test' and can't make a build in one step.

If so, this would be another thing that you shouldn't apologize for. Indeed, it's a team anti-pattern.