Another thing currently lacking in their code is two way replay protection,
something essential for any fork to avoid replay attacks and problems with transactions down the road (which would include distributions by CG and other sites).
The current status is, replay protection is a WIP right now, and will be done before the launch, which would be postponed if it's not ready in time[4].


  Taking all these things together, there's still a lot of if's, when's and maybe's. Some of those might change heavily and rapidly in the next days (at least this is my assessment).
I wouldn't expect an official announcement from CG before all important aspects are fully cleared.
This includes a firm forking date (block or timestamp), a binding statement about any premine, as well as working replay protection.
As long as these things aren't checked out, the decision about if and how CG proceeds regarding BTCGPU might still change.

I'd expect them to handle the fork similar to Bitcoin Cash, and proceed with distributions, as long as the circumstances allow it and a distribution seems reasonable.