Hi Ihar,
GBP development currently trails the main OpenStack development cycle a
bit. Hopefully this lag will shrink substantially for Liberty. We expect
to have a kilo-gbp-3 release out any day that will make sense to package
for RDO and Fedora Kilo versions, and the final Kilo GBP release should
follow soon after. Unfortunately, whats currently packaged still
requires Juno.
Can you explain what exactly it means to "move openstack-neutron-gbp
development under delorean roof"? Does this mean that the Fedora
packages would be generated from the RDO packages? I think that would be
fine. If you will be at the OpenStack summit next week, we can discuss
this there if you like.
-Bob
On 5/13/15 7:05 AM, Ihar Hrachyshka wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
now that rpm-kilo is synced from delorean to fedora/master, I see
openstack-neutron-gbp fails due to unsatisfied dependencies (it
currently requires Juno neutron).
I wonder whether that's a good time to move openstack-neutron-gbp
development under delorean roof, and leave fedora/master package as a
downstream just for koji and stuff.
In that way, -gbp package would be able to receive more attention from
neutron maintainers, getting packaging updates in timely manner, and
with review and CI applied.
I'm putting the Fedora package maintainer into CC.
Robert, since you're the maintainer of the Fedora package, could you
please evaluate the option to move the package into Delorean? I think
it would serve both RDO and Fedora and GBP interest better.
Comments?
Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVUzANAAoJEC5aWaUY1u57NIoIAK8940/9xkjZUFvO0CjnPCAc
kiugpBVn0OHaCWPhgV87dGTE3eO+aiP9/a8rLs3BejO1NZ581lDqswJRxEfsMInY
EAa5r9Zzb7eR2EPyzBnqd180yYcSNFSGEh82DBktfmlJKn+wFmjP+FsjrmVgm+le
d4uS5IedcUJJEL8YKhE2+48xnD/J/Yt8EnxOLy26iM1dEEGRKBQKrL+64PemxRw5
ae6v/lmhIVHOoZFB6qIxv2D2GlyYkXrDz+nmPuHt0kr97VkuYllwZmxcu7v7gJIG
VhT4cWs4A2UgwVG9Qb2hTPOfPMUVoDimeiwtChJdFZktSfz0Vj+8t2JhqUBjBEM=
=D4Vt
-----END PGP SIGNATURE-----