Having spent the better half of the last year within the PIFT/PIFR issue queues, chasing the holy grail of sustained testbot stability, I find myself reaching a bit of a crossroads.
Following up on my PIFT 6.x-2.7 Released post, I'd like to take a moment to walk you through another new feature which was introduced with the rollout of the new code.
We are pleased to announce that PIFT 6.x-2.7 has been released, and is now deployed on Drupal.org. PIFT stands for 'project issue file test', and is the d.o component of Drupal's automated testing infrastructure.
Having spent the better half of the last year within the PIFT/PIFR issue queues, chasing the holy grail of sustained testbot stability, I find myself reaching a bit of a crossroads.
Following up on my PIFT 6.x-2.7 Released post, I'd like to take a moment to walk you through another new feature which was introduced with the rollout of the new code.
We are pleased to announce that PIFT 6.x-2.7 has been released, and is now deployed on Drupal.org. PIFT stands for 'project issue file test', and is the d.o component of Drupal's automated testing infrastructure.