On 6/17/2014 4:53 PM, Dave Pooser wrote:
On 6/17/14 3:31 PM, "Kevin A. McGrail" <kmcgr...@pccc.com> wrote:
On 6/17/2014 4:22 PM, Dave Pooser wrote:
Did any decision on this get reached?
Yes, I believe it was committed to trunk and considered resolved.
Presumably that will be released in 3.4.1 -- is there a target date for
that release?
Hi Dave,
I was planning for a 4/30 release in keeping with our release goals
until the zones box failed. So there is no release date planned.
However, here are my priorities in order for the project (which are
subject to change and others could decide they want to do things
differently, etc):
- Get the zones replacement box work and rule updates publishing again
- Get zones backup working and make sure cron is in svn
- Make sure bug 7056 goes out for Spamhaus in rule updates ok.
- Get the new TLDs into RegistrarBoundaries
- Get TxRep polished enough so it can stay in 3.4.1
- Implement some RBL changes I want to test
- Announce the new logo formally and update the logo on the website
missing the trademark symbol
- Bug 7003 - README updates
Then there are some bugs I think should get fixed with 3.4.1 but could
slip if needed.
- Bug 7006 - sa-update version oddity
- Bug 7012 - sa-update exit
- Bug 6995 - specify user for fall back
- Bug 7010 - RuleQA hash output
- Bug 7042 - Hard Code sa-compile path
- Bug 7047 - Sorted by score for summary
- Bug 7046 - Spamc randomization
- Bug 6961 - Font test bug
All the other blockers: 6751, 3082, 3908, 6934 and 6352 should be pushed
to 3.4.2.
So Ivo, Tamer and Philip, nows a good time to start pushing towards CLAs
and getting stuff into SVN and ready for consideration on 3.4.1.
- release 3.4.1
- Get SOUGHT backup and running with people like Alex and Daniel able to
access the boxes
- See if we can fix things like bug 6400
- Get Freebsd working for builds bug 6887
- release 3.4.X or 3.5.0
For the next release after that, I've got some big ideas like the Domain
Age distributed network system as well as my URIBL work (#44488).
Hopefully will talk to a board rep about doing that under ASF sooner
than later! Plus more mundane things like DMARC support. And some even
crazier ideas ;-)
Regards,
KAM
