I agree with Leo on this. No matter how simple the change, it is always
good to go
through a testing phase. I've been bitten myself my last minute changes
in the past
myself. Its a hassle, but it gives everyone a chance to test the final
version before
the actual release.
If we are going to do another RCn then I have a minor change of my own
for the
excalibur-instrument-mgr-impl jar. If not then it can wait until the
next release.
(A typo and removing a stack dump if the state file is corrupted or can't be
accessed for any reason. It can happen if a previous JVM invocation crashed
at just the wrong moment.)
Cheers,
Leif
Vadim Gritsenko wrote:
Leo Simons wrote:
On 24-08-2005 01:27, "Vadim Gritsenko" <[EMAIL PROTECTED]> wrote:
is no reason to do yet another RC build just because of it :-) because
it is simple addition which does not alter any existing behavior.
-1 on such a process. There should be *no* difference between the RC
that is
voted on and what is eventually released. Take this seriously!
<vent>
Give me a break! PMC can release whatever it wants as long as what is
had released matches with what it had voted upon to release! If PMC
voted to release "SVN r239620", it might or might not match any of the
previous (RC or Beta or Alpha or Milestone) releases.
Moreover, one might argue there is no point in enforcing RCn == Final
policy as it lacks common sense. And in addition to this, RCn is
already out there anyway and re-releasing it is waste of bandwidth.
</vent>
But, whatever - it's your PMC.
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
