Steps to ship?
Brent Putman
putmanb at georgetown.edu
Wed Jun 25 14:16:39 EDT 2014
On 6/25/14, 1:55 PM, Cantor, Scott wrote:
>> It will take me a little while to start. Having some minor machine
>> problems at the moment after upgrading my machine to Mavericks
>> yesterday.
> Probably a good idea to cross-check against the release process page too to make sure it's accurate and current, I don't know what state that's in. I think we updated it when we did the 2.4.0 release, but I guess this is the first "real" runthrough of the steps for the whole V3 stack.
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?
More information about the dev
mailing list