A late response, but nevertheless... The problem mentioned below was a
transient state as Facebook was attempting to catch up with further
fixes in 3.8 branch. These patches have been abandoned since.
On the review requests my answer would be, do participate if you are
included, as it adds value much earlier in the cycle than waiting for
the patch to appear against master.
Thanks,
Shyam
On 12/22/2016 02:26 PM, Ravishankar N wrote:
On 12/22/2016 11:31 AM, Shyam wrote:
1) Facebook will port all their patches to the special branch
release-3.8-fb, where they have exclusive merge rights.
i) I see that the Bugzilla IDs they are using for these patches are the
same as the BZ ID of the corresponding 3.8 branch patches. These BZs are
in MODIFIED/ CLOSED CURRENTRELEASE. Is that alright?
ii) Do we need to review these backports? (Asking because they have
added the folks who sent the original patch as reviewers).
-Ravi
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
