Re: [libpcap] Consider not pushing your work-in-progress branches upstream (#420)

[Michael Richardson <mcr () sandelman ca>]

As discussed a few months ago, this is how github is being used.

1) "master" for tcpdump, libpcap and tcpdump-htdocs lives on
            http://github.com/the-tcpdump-group
   We pull daily from github master to the server at bpf.tcpdump.org.

2) release branches live on bpf.tcpdump.org, and are pushed daily to github.
   The script looks like:

(cd libpcap && git fetch -f github master:master &&
        git push github $(git branch | grep libpcap-) &&
        git push --tags github )
(cd tcpdump && git fetch -f github master:master &&
        git push github $(git branch | grep tcpdump-) &&
        git push --tags github )
                                
3) vulnerabilities are developed at
   git+ssh://bpf.tcpdump.org/tcpdump/master/git/tcpdump-security

   which is only accessible to developers with accounts on bpf.

Previously, all branches on bpf were pushed to github, but now only branches
that start with tcpdump- and libpcap- are pushed.

A security release 4.7.2 is being prepared today, and once the distro folks
have been notified so that binaries can go out, it should go public within a
few days.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr () sandelman ca  http://www.sandelman.ca/        |   ruby on rails    [ 
        

_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers