Re: [tcpdump-workers] Tcpdump 4.6 delayed

2014-06-16 Thread Michael Richardson
Romain Francoise wrote: >> Yeah, my bad; was sick that weekend, and stuff... happened. > No problem. >> How about July 1? > So -rc1 on July 1, then release a week later? Or -rc1 in the meantime, > and release on July 1? (Works for me either way.) -rc1 on July 1. Release a

Re: [tcpdump-workers] Tcpdump 4.6 delayed

2014-06-16 Thread Romain Francoise
Michael Richardson writes: > Yeah, my bad; was sick that weekend, and stuff... happened. No problem. > How about July 1? So -rc1 on July 1, then release a week later? Or -rc1 in the meantime, and release on July 1? (Works for me either way.) ___ tcpd

Re: [tcpdump-workers] Tcpdump 4.6 delayed

2014-06-15 Thread Michael Richardson
Romain Francoise wrote: >> I was way too at this ietf89 to build changelog and push release button. >> I propose to release at Easter. (April 21) > So it looks like this never happened? Yeah, my bad; was sick that weekend, and stuff... happened. How about July 1? _

Re: [tcpdump-workers] Tcpdump 4.6 delayed

2014-06-15 Thread Romain Francoise
Michael Richardson writes: > I was way too at this ietf89 to build changelog and push release button. > I propose to release at Easter. (April 21) So it looks like this never happened? ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org