On Tuesday 17 November 2009 07:23:33 Warren Togami wrote: > Time for 3.3.0 beta? Anything else we should do first?
[Warren, elsewhere]: > I propose we release 3.3.0 beta ASAP, after the scoring commits I just made > in Bug #6155. > Prior to 3.3.0 final release we should attempt to fix this bug properly. > If we cannot, then we should minimally make Bug #6232 not dangerous. I have some possible solutions for Bug #6232, just haven't decided yet which one is closest to the intentions of the Net::DNS writers. The docs about a supposed internal representation is sketchy, the intention has to be deduced from source code. Docs on the underlying Net::DNS::RR is much more explicit. Before the beta I think the problem reports with implications to compatibility should be resolved, at least to the point where no further incompatible changes after a beta will be necessary. In particular I have Bug 6187 and Bug 6203 in mind. About the 6203, I have some stats collected. Also the AWL race condition: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4642#c1 is worrying me. I'm using a workaround (attempt INSERT first, and if that fails do the UPDATE), but the change is nontrivial, and depends on a unique key constraint failing to work properly. If you like, I can submit it for consideration - can be reverted later if not approved. An alternative is to use ON DUPLICATE KEY UPDATE, but that seems not to be liked according to Bug 5998. The suggestion in Bug 4508 (the patch in Comment 3) seems quite useful and not too intrusive on the current/default usage. Any thoughts on that? Do we need a CLA from its author? Btw, there are like two or three small documentation-change requests there. If someone has some spare cycles, it would be nice to get rid of these problem reports. Mark
