ant elder wrote:
On Tue, Jul 15, 2008 at 7:21 AM, Simon Nash <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:Simon Nash wrote: ant elder wrote: Luckily i started RC2 last night but then decided to finish it off this morning so there's still time to get that in. Thanks. I'm about to get on a plane so I won't have connectivity for the check-in until I land at LAX later today. The long flight will give me plenty of time to review and regression test the changes, but the downside is that I won't be able to do the commit until some time around midnight UK time. I hope this doesn't cause too much of a problem. I'm sorry to report that this is still not ready. I'm seeing a failure in one of the samples with my changes applied. Please go ahead with the next 1.3 RC when you are ready and don't hold it any longer for this.Is this fix something that must get in to the 1.3 release or is leaving it till 1.3.1 ok? If it must be in 1.3 then i'd like to hold off making the next 1.3 release candidate till the fix is available, mainly to avoid release review fatigue. Does this sound ok?
Sorry for the delay in responding. I am in OASIS meetings this week and I have very limited opportunity to work on this problem or to read email. I'm still trying to determine the cause of the sample regression, and I can't say how long it will take. Given the uncertainty, I don't think we should delay the 1.3 release to get this in. Simon
...ant
