Apologies for breaking the Jenkins v2 build

[Tom Zeller]

On Mon, Mar 2, 2015 at 2:54 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 3/2/15, 3:51 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>>
>>On 3/2/15 3:45 PM, Tom Zeller wrote:
>>> I thought that -SNAPSHOT versions could/should point to the parent
>>> TRUNK-SNAPSHOT.
>>
>>Not as documented in the wiki, no.  When we release a new minor version
>>(e.g. 3.0.0, 3.1.0, etc), it gets "locked" to a specific version of the
>>parent.  All patch releases of that minor version use the same parent,
>>except under extraordinary conditions.
>
> 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.
>
> 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.

I'm confused. If we can't change the parent version outside of a minor
release, then we can't update a third-party library for a bug fix in a
patch version.