I want to agree with you, but actually can't. He should not be responsible. Because he already failed - he should have had that under control while he was worki

I want to agree with you, but actually can't. He should not be responsible. Because he already failed - he should have had that under control while he was working on it, from the very first day. Not on his notice period. We push a mentality of devops and the whole team (regardless of their position) being responsible for the final product. Push interdisciplinary attitude, where fine defined borders of each team/job fade. That developer IS responsible for that and if it's not covered by the time of his notice period it means both him and his management failed in some extent.