Skip to main content Skip to search
Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see?
Main menu
  • Drupal.org home
  • Discover Drupal
    • Drupal Core
    • Drupal CMS
    • Drupal AI
    • Case Studies
    • Drupal for Government
    • Drupal for Higher Education
    • Drupal for Nonprofit
    • Drupal for eCommerce
    • Drupal for FinTech
    • Drupal for Healthcare
    • Drupal for Enterprise
    • Drupal for Retail
    • Drupal for Travel & Tourism
  • Build with Drupal
    • Download Drupal
    • Documentation
    • Getting started
    • Local Development Guide
    • Developer Resources
    • Drupal CMS User Guide
    • Drupal User Guide
    • API
    • Modules
    • Themes
    • Recipes
    • Site Templates
    • Issue queues
    • Security Advisories
  • Partners & Services
    • Find a Drupal Certified Partner
    • Become a Drupal Certified Partner
    • Find a Hosting Provider
    • Find a Migration Partner
    • Find Training
    • Drupal Steward
  • Community
    • About the Community
    • How to Contribute
    • DrupalCon
    • Events
    • Jobs / Careers
    • News & Blogs
    • Forum
    • Slack
    • Newsletters
    • Drupal Swag Shop
  • Support Drupal
    • The Drupal Association
    • Donate
    • Become a Partner
    • Become a Ripple Maker
    • Become a Drupal Sustaining Member
    • Drupal Swag Shop
  • Get Started
    • Try Drupal CMS
    • Try Hosting
Return to content

Search form

  • Log in, view profile, and more
    • Log in
    • Create account
Drupal.org
ModulesProject issue file testIssues

PIFT 2.3 Requirements

Closed (won't fix)
Project: 
Project issue file test
Version: 
6.x-2.x-dev
Component: 
Documentation
Priority: 
Normal
Category: 
Task
Assigned: 
boombatower
Reporter: 
boombatower
Created: 
17 Jun 2010 at 03:00 UTC
Updated: 
16 Sep 2015 at 04:37 UTC
Jump to comment: Most recent

Tracking requirements for the 2.3 release.

#675460: Ensure/Refactor cron_retest() query to only re-test the last file on an issue; Automatically retest RTBC patches
#698932: "test_dependencies" for dependencies / integration tests
#744658: Retain re-test color after sent
#714466: Comment ID is placed in re-test link on filename twice
#698392: Retest branches automatically on time and commit trigger
#829850: Add drush command for cron to allow for decreased wait time
#698386: Integrate branch tests with project page/releases
#698384: Per project branch filter
#879662: Use test.directory.review instead of module list
#981216: Update argument keys for pifr 2.3

Comments

boombatower’s picture

Comment #1

boombatower commented 17 June 2010 at 03:00
Title: PIFR 2.3 Requirements » PIFT 2.3 Requirements
  • Log in or register to post comments
Mixologic’s picture

Comment #2

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented 16 September 2015 at 04:37
Issue summary: View changes
Status: Active » Closed (won't fix)
  • Log in or register to post comments
Contribution record
Add child issue, clone issue
Infrastructure management for Drupal.org provided by Tag1 logo
Need a Drupal 7 extended support partner? Consider Tag1.

News items

  • News
  • Planet Drupal
  • Social media
  • Sign up for Drupal news
  • Security advisories
  • Jobs

Our community

  • Community
  • Services, Training & Hosting
  • Contributor guide
  • Groups & meetups
  • DrupalCon
  • Code of conduct

Documentation

  • Documentation
  • Drupal Guide
  • Drupal User Guide
  • Developer docs
  • API.Drupal.org

Drupal code base

  • Download & Extend
  • Drupal core
  • Modules
  • Themes
  • Distributions

Governance of community

  • About
  • Web accessibility
  • Drupal Association
  • About Drupal.org
  • Terms of service
  • Privacy policy

Drupal is a registered trademark of Dries Buytaert.