|Summary:||net/exabgp upgrade to 4.0.6|
|Product:||Ports & Packages||Reporter:||Olivier Cochard <olivier>|
|Component:||Individual Port(s)||Assignee:||Ryan Steinmetz <zi>|
|Severity:||Affects Only Me||CC:||freebsd, pi, sergey, w.schwarzenfeld|
Description Olivier Cochard 2018-05-26 06:23:52 UTC
Created attachment 193707 [details] patch to upgrade exabgp to 4.0.6 Hi, here is a proposal for net/exabgp ugprade: With this upgrade, the package name is python-version dependent (become "py36-exabgp 4.0.6" as example).
Comment 1 Ryan Steinmetz 2018-05-26 12:11:29 UTC
This is still a pre-release/development version. The latest stable/official release is 3.4.25. Do you need features in 4.0.6?
Comment 2 Walter Schwarzenfeld 2019-02-12 16:59:07 UTC
Version 4.0.10 released. https://github.com/Exa-Networks/exabgp/releases
Comment 3 Ryan Steinmetz 2019-02-12 17:14:28 UTC
4.0.10 is still pre-release. Rejecting until upstream considers it ready to replace the 3.x branch: "This version is most likely the last one before we consider the master branch ready to replace 3.4.x."
Comment 4 Leo Vandewoestijne 2019-08-01 13:07:43 UTC
At https://github.com/Exa-Networks/exabgp/releases I now see 4.1.2 having the badge "Latest release". But does that mean it's a stable release or just the "latest release"? Reading the comment: "The control API / CLI command are however not yet frozen and will slightly change before a stable 4.1.0 release." ...plus the name "ISO-release" (for 4.1.1) sounds to me that it became stable last month. Currently I don't install ExaBGP in production because it requires python 2.7