Hi Alan:
Thanks for pointing me to the RabbitMQ packages, we're going to test
those internally and report if we run into the issue again.
I do agree with what David has pointed out in that there should be a
process setup in order to make sure that the shipped packages that
come with RDO (at least the supporting ones such as MariaDB/Galera,
etc) should be good-to-go. I imagine this might make things a bit
more difficult in terms of testing them, so I'm not sure what would be
the best path to take in this case.
Thanks
Mohammed
On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec <apevec(a)redhat.com> wrote:
On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard
<dms(a)redhat.com> wrote:
> I think with OpenStack components it's easier, there's branches and we
> build/test them throughout the lifecycle.
> Once we have the proper testing in place, we can update those more frequently.
Ideally same would apply for dependencies like rabbitmq, mariadb, we'd
update frequently and release after testing but also vetted by package
maintainers.
Let's start by this last part: I'll check that components in RDO
bugzilla have correct default owner then we setup nagging like
https://fedoraproject.org/wiki/Upstream_release_monitoring for few
critical dependencies.
Alan
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com