> Committers/PMC: > Please vote to release 3.4.0-rc3. Looks good, thanks!
+1 from me. > I'm now running it on one production > system and have been monitoring it for a while. So far so good! Same here. > Files at http://people.apache.org/~kmcgrail/devel/ > Proposed Announcement follows. Just comitted some small tweaks to the announcement text. > Discussing blockers to a real 3.4.0: > > From my perspective, I'm working on some RBL changes. Not really > blockers, but it's my focus right now. Ok. > I also think Bug 5503 needs to be completed because it could change > headers people expect and a 3.4.0 major release is the time to do > something like that. > We also need to work on these issues: > Bug 6422 to test CPAN > Bug 6639 re: Suse 11 and CPAN I have no opinion on this. > After that, I'm hoping to at least spend a few hours documenting some of > the things AXB pointed out: > > New configuration options - Imo - these should be documented: > > Plugin/WLBLEval: > > blacklist_uri_host example.net > blacklist_uri_host somehost.example.net > > whitelist_uri_host example.org > whitelist_uri_host somehost.example.org > > Addition: > > - Disable lookups for a specific DNS list (instead of zeroing out > rules) > > dns_query_restriction deny someBL.example.org > > - If possible some minimal rule samples for > > "added the following sub-options to the tflags setting" > autolearn_force, maxhits=N, ips_only, domains_only, a, ns. > > A lot of features like these remain unused because they're either > very hidden or not loudly documented with sample rules. Good. A bug 6953 worries me a little, as some Linux folks which do have module IO::Socket::INET6 installed but not the IO::Socket::IP may come across this issue. I have added a paragraph and a ref to this bug into the announcement text. I don't have a good solution. > Then we should be able to get 3.4.0 out the door which leads to these > issues: > > Bug 6885 to switch the website's publishing method will be needed to > update the website to announce the release. > > Work on post-3.4.0 issues: KAM will be working through the rest of the > build/README file and expect lots of issues / problems that will need to > be overcome to switch to 3.4.X. Ok. Mark
