Forwarding to gluster-devel. We're aiming for an alpha3 release "ASAP".
Stay tuned for more info on 3.3.2-qa releases, coming up Real Soon Now. -JM ----- Forwarded Message ----- From: "Jeff Darcy" <[email protected]> Sent: Friday, April 12, 2013 8:39:14 AM Subject: Re: Status of 3.4 alpha/beta bugs > Here are the bugs associated with the 3.4beta1 tracker (918917). I'm > asking for three actions from each of you. > > (1) If a bug is assigned to you, please verify its status. POST means a > patch has been posted, MODIFIED means the patch has been merged in > master, ON_DEV means it has been merged in the release-3.4 branch, > nothing should be ON_QA until it's actually in a tagged and published > RPM. Downstream status is irrelevant. > > (2) If you think a bug is in the wrong category, let me know. > > (3) If you know of other bugs that should be on one of these lists, let > me know. > > Once I'm sure the lists are correct, I'll create a separate 3.4alpha3 > tracker for those bugs, and track down all of the patches associated > with each bug on the first two lists. Thanks for all of your help. List below has been updated to reflect last night's flurry of merges, and to remove the list of updates that are already in the 3.4 branch. Please pay particular attention to the list of patches needing backports to 3.4alpha3, since there's not much of "this week" left. Kudos to Shishir in particular for getting a bunch of bugs (some not even his own IIRC) off these lists. *** Need fix/backport for alpha3 (this week) 847214 ([email protected]) glusterd operations hang if the other peers are down 924215 ([email protected]) glusterd crashes when rdma.so not present 927146 ([email protected]) AFR changelog vs data ordering is not durable 948686 ([email protected]) Glusterd updates list of volumes and peers in a race'y manner. 950048 ([email protected]) "gluster volume sync" command not working as expected *** Need fix/backport for beta1 (before Summit) 762989 ([email protected]) Possibility of GlusterFS port clashes with reserved ports 764924 ([email protected]) Instability and High Server Memory Usage When Using RDMA Transport 765051 ([email protected]) Use librdmacm for connection establishment. 794699 ([email protected]) Can not tollerate failiure of a brick in replica volume 839810 ([email protected]) RDMA high cpu usage and poor performance 887301 ([email protected]) Container listing of objects is sorted resulting is higher latency in response time 913544 ([email protected]) stub unwind of ftruncate leads to crash 916372 ([email protected]) NFS3 stable writes are very slow 919352 ([email protected]) glusterd segfaults/core dumps on "gluster volume status ... detail" 919990 ([email protected]) Crash in server_rpc_notify 928341 ([email protected]) Enable write-behind for gluster nfs server process 950056 ([email protected]) nfs.rpc-auth-allow does not work as expected with FQDN _______________________________________________ Gluster-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gluster-devel
