At the moment the master branch of the registry provides compatibility with the ffnet. Now we have changes coming up that would break compatibility or require significant effort to keep compatibility (Substrate update #508 and consensus changes #475). This is why we are considering to stop maintaining compatibility between the
master branch and the ffnet. In particular this would mean that the node, client, and cli build from
master will not work with the ffnet. This also means we would stop releasing updates that work with the ffnet.
The alternative would be to put of the changes or work around them. Comparing the effort and delay to value of continued support for the ffnet we don’t think it’s worth it.
We will keep the our ffnet infrastructure (miners, validators, rpc nodes) running until we start a new public network. Upstream does not use the ffnet to develop or test at the moment. (They use the emulator). Should the need a shared network at some point we can use the devnet or start a ffnet successor.
@igor and I agree on this. We’re waiting for input from @NunoAlexandre and @lftherios on this and would like to reach a decision on Monday, 6 July. If we agree to move forward with this we’ll start accepting changes to master that break compatibility.