Apologies for breaking the Jenkins v2 build

[Brent Putman]

On 3/2/15 3:54 PM, Cantor, Scott wrote:
> This is tied to the "third party dependencies can never change" issue, the 
> idea was that you'd never change the parent outside a minor update.

Yes, in part.  I think in general the idea is that other aspects of the
build other than dependencies (plugins, etc) were also not supposed to
change in a patch.


>
> Of course since we're at 3.1.0 right now anyway, it's not a mistake at the 
> moment since we're back to having to change the parent for that release. 
> But then it's supposed to stay locked to that number until we branch or 
> decide to go to 3.2 for the next trunk release.

Yes, agreed (mostly).  I think the docs are a little murky about this,
particularly around when to branch, trunk vs branches, etc.