On 3 Aug 2016, at 15:25, Jay Shaughnessy wrote:
responsibility. If you are responsible for the src-dep being in
master
then you are responsible for ensuring it doesn't block the release. So,
by Friday, or Monday at the latest, either get rid of it yourself by
doing a release of the component and updating the pom, or, find someone
And todays release build showed that this is not feasible,
as a src-dep indeed remained in master and broke the
release build.