One of the problems we've always had that delays deployment of PIFR and PIFT code is that it has been hard to test. But now we have a workable test environment, consisting of three parts:
- A drupal.org clone, http://rfay.redesign.devdrupal.org, housed on stagingvm.drupal.org. (This is one of the new tricked out development sites that are now available to people who want to improve drupal.org)
- http://qa.scratch.drupal.org, housed on stagingvm.
- Testbots as needed can be spun up either as local VMs and configured to pair with qa.
With this approach we can be far more confident of new code in PIFR or PIFT before deploying it.
If you need access to any of these systems, let me know. We can also add systems and update the d.o clone database easily.