> This means if we have to > drop support for older Net::DNS, I would support that as well.
No need to, this is not in question. > Right now, as I understand it: > > A) you've already patched sa-update in trunk to handle this and it works > with older and newer Net::DNS versions Right. > B) Rather than change our backend automated DNS to add the kludgey > entries and hope they work and aren't destroyed in the DNS ecosystem, if > the community demand exists, we push a new 3.3 release with the same patch. > > Overall, 3.4 has been far too long in the making and contains a > wonderful number of bug fixes. Running 3.3 at this point is just not > what I would recommend to anyone. I agree that pushing 3.4 out the door as soon as possible is the right strategy. Trying to make a 3.3.3 release seems to me an unnecessary effort. Regarding the very shory-term future, I see the following choices (in no particular order): 1) hope that Linux/Unix distros pick up and apply the small patch to sa-update; contact them if necessary; meanwhile answer concerns on the mailing list, pointing people to apply the patch to SA or to downgrade their Net::DNS to 0.68; 2) ask the Net::DNS folks if they'd be willing to put back the unconditionally double-quoted form for 0.71, and keep it there for at least until SpamAssassin 3.4 really hits the streets; meanwhile suggest people to switch Net::DNS to 0.71 or to 0.68; 3) make a 3.3.3 release with just this small patch applied; 4) go with the quick-fix / kludge workaround; Looking back at what I just wrote, the #2 looks to me the most appealing. Mark
