[openstack-dev] [neutron][vmware][stable] vmware-nsx has no releases

Gary Kotton gkotton at vmware.com
Mon Aug 17 17:44:14 UTC 2015


Hi,
There are still a few extra stable back ports that we need to make.
In addition to this I think that we should try and sync all of the etrnal projects for a common release.
Thanks
Gary

From: "mestery at mestery.com<mailto:mestery at mestery.com>" <mestery at mestery.com<mailto:mestery at mestery.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, August 17, 2015 at 9:59 AM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron][vmware][stable] vmware-nsx has no releases

On Mon, Aug 17, 2015 at 7:05 AM, Ihar Hrachyshka <ihrachys at redhat.com<mailto:ihrachys at redhat.com>> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi VmWare folks,

I wonder whether we can get some actual release tags for stable/kilo
branch of the repo. Lack of any consumable tarballs does not help
packagers that want to just get the tarball from pypi and use it as a
base.

I tried to follow the dumb way of generating a tarball from github,
but pbr complains about lack of sdist or git when I call to 'setup.py
build'. Putting egg-info directory inside the tarball does not help.

I think it would be better for everyone if tags and tarballs came from
upstream.

I suspect other spinned-out neutron drivers could have the same
problem. Can we somehow make sure they are releasing deliverables and
not just git repo?

We will talk about this at the meeting today but yes, the plan is to get releases for these. So far we've only discussed stable releases, but I think the plan to release master snapshots would be good. It would give the packagers a chance to package these.

Ihar, lets work to make this happen tomorrow or Wednesday.

Thanks,
Kyle


Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJV0c4PAAoJEC5aWaUY1u57M2cIALuH2MByojn7N1byCV4ctTal
NPsUTgFyzDEXSU1QSgobR6x1uP8hYBW2RSUqnh4tR+SoYz/vmF1IvwXl53tb3Jnq
4MTwXbom3xPgjUYsUep5TAhPglMXf4LwnTYejhqc78IOlNg7tAC0U/yA2ZitFhm2
5zWsec1zggsku4aIMCz06bFwgQHwYl57uHBB/iqO+fbRIGZLkcGrbjiucKIlQqsF
uv9GoymuwOEVjmTtooQBoVQ0J2f/yZYswcRBExbJU78eIP89+A2kDL9nA4fFFhCl
b5Yus6oJDn/XMaU8PWZ8TptWEOY3Z80wbCRZk27FNObSb6yLs+2ZS7Rge+ZCz5s=
=VP83
-----END PGP SIGNATURE-----

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150817/e35b24db/attachment.html>


More information about the OpenStack-dev mailing list