DrupalCI Test Runner - D8-Accelerate Priorities

Goal: ‘Release-ready’ codebase for drupalci_testbot project

  • Address existing issues blocking creation of a DrupalCI alpha release.
  • In Scope for Alpha:
    • ‘Mandatory’ capabilities and new features
    • e.g. Publishing Job Artifacts
    • e.g. Enhanced logging capabilities, with verbosity support
    • Any bugs which can occur during simpletest test runs, affecting testing stability
    • New DrupalCI features (regressions relative to PIFT/PIFR)
      • e.g. Incorporate syntax linting into test runs (testing feature regression)
    • Critical bugs in non-testing areas of the codebase
    • Stability enhancements
    • Performance enhancements
    • New functionality related to environment coverage
    • New functionality related to specific ““Drupal 8 core” testing requirements
    • Functionality related to integration with Drupal.org (triggering tests / exposing results)
    • In-code documentation
    • External documentation
  • Out of Scope:
    • Non-critical bugs which do not affect test runs or D8 integration
      • e.g. local testing user interface problems, etc

In-progress Issue Hitlist and progress will be tracked via google docs spreadsheet:
https://docs.google.com/spreadsheets/d/1SmweOsG2D8xRuxsF-NtR4HdXPaDwBXWD...

Comments

jthorson’s picture

Issue summary: View changes

Adding customer attribution

jthorson’s picture

Issue summary: View changes
jthorson’s picture

Google spreadsheet updated ... I'd appreciate some DA review/input/participation here.

hestenet’s picture

We've made some updates to our priority hit lists in:

As you know our urgent priorities coming up to Barcelona are:

  1. Unblock D8 release
  2. Disable PIFT/PIFR as soon as possible for financial reasons.

I've tried to add some names next to issues to reflect who we think will be working on those priorities - and I've added your name, @jthorson, next to the items where we think your expertise would be helpful?

Mostly this to help us avoid stepping on each other as we keep plowing through issues. Your spreadsheet has a number of additional issues beyond our two Plans that I think we certainly won't step on.

Hopefully we can talk through this a bit more on tonight's DrupalCI call.

Mixologic’s picture

Status: Active » Closed (outdated)