These are chat archives for Exa-Networks/exabgp

13th
Jan 2016
Thomas Mangin
@thomas-mangin
Jan 13 2016 16:03
@tmmorin I will create a 4.0 branch. I will not update it until the release but it will give you some ‘stable’ code to work on. The data structure for the classes you uses should not change much before the release anyway.
Done
Thomas Morin
@tmmorin
Jan 13 2016 17:33
hi @thomas-mangin
having a 4.0 branch is not really what would help, really the thing that would help is having a 4.0_alpha_xyz pip release
but I haven't checked if this is something that pipy accomodate with easily
hmm, forget about that suggestion:
http://blog.ziade.org/2011/02/15/do-not-upload-dev-releases-at-pypi/
-> pushing dev releases to pypi is explained as a bad idea
Thomas Morin
@tmmorin
Jan 13 2016 17:39
hmm, the post above is old -- maybe that would still be doable
Thomas Mangin
@thomas-mangin
Jan 13 2016 17:39
You have a tag on Github
I would not want to push to Github. You can have git dependencies between
Thomas Morin
@tmmorin
Jan 13 2016 17:46
you meant push to pypi I guess
yes, it seems that it is hard to publish dev code to pypi , and play well with pip dependency resolution
Thomas Mangin
@thomas-mangin
Jan 13 2016 17:47
Repos so you do not need to copy and paste code
Thomas Morin
@tmmorin
Jan 13 2016 17:47
seems hard to avoid automatically pulling a dev release when what you want is a stable release
Thomas Mangin
@thomas-mangin
Jan 13 2016 17:48
I would be happy to keep the new 4.0 branch for you
Sorry using mobile phone and fighting it
Thomas Morin
@tmmorin
Jan 13 2016 17:49
the offer is nice, but a branch or a tag on github is not that helpful currently
the issue I have is that my plan would be to use code exabgp code that currently is not yet on pypi, in the continuous integration test in openstack (for networking-bgpvpn)
but the openstack continuous integration tools do not allow cloning non-openstack repos
which is why having the code currently in master, pushed on pypi, would have helped
if possible
having a 4.0 branch, does not help address openstack CI tooling constraints
Is this allowed
Thomas Morin
@tmmorin
Jan 13 2016 17:58
yeah, I know about submodules
I have to check, but I guess they would raise the same questions than cloning repos
from the point of view of the practice encouraged for the openstack CI
being part of openstack has implications in terms of trying to not do things that other projects don't do
maybe we don't have to go through all this questioning: do you have an idea when 4.0 maybe releasable ?
Thomas Mangin
@thomas-mangin
Jan 13 2016 18:01
Which part of 4.0 do you need as I could perhaps back port to.3.4 what you need