https://bugzilla.redhat.com/show_bug.cgi?id=1562670
--- Comment #4 from Prashanth Pai <p...@redhat.com> --- > I guess that is not an ideal thing to do. Either we have to keep the goal as > every release rebase Every release rebase would be ideal. > There will be no chance of knowing when we will have 'all the changes' > completed. All the changes planned for a particular release. I think glusterfs release 5 has some API changes planned (that got pushed from 4.1 plan). When all those API changes are in, we can make libgfapi-python rebase to those changes. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=oQx2xHUzVg&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
