[platform-releng-dev] What to do for Kepler SR2 RC4 build?

[David M Williams <david_williams@xxxxxxxxxx>]

As far as I know, there are no more fixes
going into RC4? And, I've heard some mention "we may not need an RC4
build". 

Even if no more fixes going into it,
I propose we still have the one scheduled for 8 AM Wednesday. The reason
is I would like to delete our "cached M-build repo", and let
the whole thing re-clone and rebuild. 

If it turns out to be the same, identical
build, then nothing lost. But ... 

There's something mysterious going on
with at least one of our build machine's cached repos, as illustrated by
some 
oddities in last night's N-builds. Such
as see details in 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=419647#c31

I guess I'm a little worried we may
not be properly "cleaning" and "resetting" the repo
to a pristine state each build. 
So, I'd hate to come out with SR2 and
later learn it was missing some commits. 

Perhaps the N-build is "worse",
since there are so many of them ... but I believe a "fresh run"
is probably prudent. 
(Probably should do this "before
each milestone" and "at the start of RCs" ... just to be
safe ... at least until we get to the point of 
not producing such "dirty"
builds? (Bug 420078
) Which probably won't be for a long
time? ). 

Let me know if any objections, 

Thanks,