Is there a downside to having it? A positive is it gives a snapshot of
everything for each release.
I'm not at fan of having a snapshot of the Hadoop swift patches compiled
into a jar and stored in the repository. I'd prefer that it is hosted
elsewhere.
Best,
matt
On 08/19/2013 04:37 PM, Sergey Lukjanov wrote:
Hi Matt,
it is not an accident that savanna-extra has no tarballs at
tarballs.o.o, because this repo is used for storing some date that is
only needed for some stuff like building images for vanilla plugin,
storing Swift support patch for Hadoop and etc. So, it looks like
that we should not package all of them to one heterogeneous tarball.
Sincerely yours,
Sergey Lukjanov
Savanna Technical Lead
Mirantis Inc.
On Aug 20, 2013, at 0:25, Matthew Farrellee <m...@redhat.com> wrote:
Will someone setup a tarballs.os.o release of savanna-extra's master
(https://github.com/stackforge/savanna-extra), and make sure it gets an
official release for 0.3?
Best,
matt
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
