ROOT Team Meeting 25th March

## Shift:
- failures on windows
- gh issues from Fixathon not assigned 
    - let's assign the issues but they still have labels

## Meeting summaries: 
- Roofit meeting 
    - problem with newer versions + ATLAS/CMS fits and how to debug those
    - further plans with Roofit and AD (jitting time reduction)
- quarterly report to be announced soon - talk about releases with experiments 

## Topics

* Status of the builds 

    * tests that are failing - PyROOT tests on recent linuxes (fixed by new cppyy)
    * TCling load and unload --> test is failing so it's disabled in master, the disabling should be backported to 6.30 and 6.28 
    * a few cracks in Windows 
    * how do we proceed with regularly broken tests? 
    * broken tests from the start (esp Windows) -- turn them off at least for the time being, spend some time later to fix them 
    * how many flaky tests do we have? - 2 or 3 sporadically (for example: distr RDF) 
    * maybe disable those tests but make sure they are not forgotten 
        * revisit before the release?
        * create a gh issue and tag as a blocker for the next release 
        * Danilo will take care of this
    * use gtest skip - add a comment why you disable this test or disable tests with ctest if it is not a gtest
    

* Path to ROOT 7
    * a reminder we should take a look into this 
    * not right now (we have limited resources) but in a few months yes