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.