**** Now moved to openstack/networking-bagpipe (but still usable standalone) ****
Very childish top post ..
hey :) nice to see you here
let me just take the opportunity: any idea when ExaBGP 3.5 would ship, that would allow to drop the bagpipe-bgp branch which has its own fork of exabgp, and switch to the new branch that depends on everything we added/cleaned'up in exabgp 3.5
ExaBGP 3.5.0 will not happen, ExaBGP 4.0.0 will. I spent the last month rewritting fully the configuration parser - this is not completed but well under way and has reached feature parity with 3.4. Next to do is a cleanup of the NLRI ( with INET, LABEL, MPLS - currently LABEL does not exists ), of the FSM (which is wrong on master). Then I have 4/5 features request that need to go in 4.0. So … the short answer is surely at the end of the summer.
Do you want me to create a bagpipe-bgp branch ? You could use it with git-submodule to do what you need now ?