On Fri, Apr 5, 2019 at 10:48 PM Poornima Gurusiddaiah <[email protected]> wrote:
> Hi, > > We had a critical bug [1], that got introduced in gluster release 5. There > are users waiting on an update with the fix. Hence requesting for an out of > band release for 5.6. Myself and jiffin, volunteer to do some tasks of the > release- tagging(?) testing. But would need help with the builds and other > tasks. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1673058 > [2] https://review.gluster.org/#/c/glusterfs/+/22404/ > > +1 to the idea of doing an out of band release. I am also wondering how we can prevent significant regressions from being part of a release in the future. One proposal I have right away is to ensure that functional (glusto?) and performance (gbench?) regression tests are completed prior to a release. Both glusto and gbench might need some attention from us to be able to use those frameworks effectively for release testing. Are there better thoughts or proposals for preventing issues of this nature? Thanks, Vijay
_______________________________________________ maintainers mailing list [email protected] https://lists.gluster.org/mailman/listinfo/maintainers
