- This was the first NetCAT with a three week cycle, to support the quarterly release schedule of Apache NetBeans.
- Given the shortness of the cycle, the focus was on release drivers (JDK 11 and PHP) only.
- Potentially, each NetCAT program should now focus on release drivers only, though given that we'll be releasing more frequently, that means all features should be covered at least once per year.
- More or less continuous NetCAT, i.e., soon after NetCAT 10.0 is complete, we should focus on NetCAT 11.0, specifically focused on the Apache NetBeans 11 release driver: Java/Jakarta EE.
- In between NetCAT cycles, should evaluate the test specs themselves, how correct are they, how up to date, how complete.
- Tribe leaders were not made use of, consider using them next time, to divide the load of managing the process.
- Each tribe leader should know how to assign test specs, i.e., have permissions to do so.
- Maybe each participant should be able to assign test specs to themselves.
- Only one test spec should be assigned to a participant at a time, preventing one person having 5 and doing none, creating the impression that they're working on some, but in the end none.
- Build up a list of reliable NetCATters, i.e., those who completed what was assigned, and can be relied on to follow through in future too, especially important in shortened cycle.
- Students at universities and colleges can be approached to participate in NetCAT, e.g., Fontys Venlo – lecturer – their lecturer is NetCATter Pieter van den Hombergh teaches there and who has suggested this.
- Target completion should be at least 80%.
- A week before the end of NetCAT, i.e., end of the 2nd week, the status of NetCAT should be assessed, including blockers.
Page History
Overview
Content Tools
Apps