As I understand fix for this bug is already included into "6.0-mu-2". We just need to create release notу for 6.0-updates
As I understand fix for this bug is already included into "6.0-mu-2". We just need to create release notу for 6.0-updates