Steps to ship?
Brent Putman
putmanb at georgetown.edu
Wed Jun 25 14:35:18 EDT 2014
On 6/25/14, 2:16 PM, Brent Putman wrote:
>
> I think the only real thing that's not right or applicable here is that
> we shouldn't invoke the lock script to lock the projects to the version
> of the parent. Since I imagine we want to allow for changes to the
> parent before the release and given that we don't really have any way
> currently to "unlock" the projects, I think we should just leave as-is
> for now. In the tag I'll manually update the parent version to point to
> the v3 parent we're about to tag (which looks like it will be version
> '3'), so the only practical difference is that the .checkstyles will
> still point to the parent trunk. I doubt we care about that, right?
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?
More information about the dev
mailing list