Steps to ship?

[Brent Putman]

On 6/25/14, 2:50 PM, Tom Zeller wrote:
>>> Actually, to amend that:  java-support and spring-extensions should be
>>> locked I believe, as we aren't doing alphas for those. These are the
>>> actual releases of 3.0.0 and 1.2.0 respectively.  I'll lock them in the
>>> tag, but not in the trunk.  Does that sound right?
>> I think so. I think we talked about using a svn cp to basically change the local copy but copy that directly to the tag so that the checked-in trunk would never have the wrong info?
> That sounds right, as far as I remember.

Yeah, I always do the 'svn copy' of working copy to URL when I tag. 

For those 2, given that they are actually releases, the intention of
Chad's process is that the release on trunk does get locked to the
particular version of the parent.  However, it's always been unclear to
me what one does on the *next* major/minor release when you need to
relock to a new version of the parent.  It would make more sense if we
always cut a branch for each minor/major version or something, but we
don't currently have that, as far as I understand it.  In any case, I'm
just going to leave the trunks of these 2 untouched for now, and we can
resolve later.