- Establish some "publish criteria" before declaring a quarterly branch as the "new" official branch. Right now there are no criteria other than trying to read through lists of error summaries. We need to be able to create some kind of automated figure-of-merit for each particular build. My view is that portsmon could be augmented to help with this, but in any case, we need this functionality.
- It is difficult to evaluate regressions on individual runs. A "test instance" of portsmon should probably be used to do this. A method already exists to display these data but even the portmgrs do not understand it well. (FWIW, portsmon does not "know" what builds are -exp builds; it treats all build inputs the same. It would be far easier to instantiate a separate "test" portsmon that takes input from those builds to display to those specifically interested, than to rearchitect the UI. This would continue to keep those data out of the current instance, which is intended for the general public as well as ports infrastructure developers.) (In fact, the development instance in Austin does exactly this, as well as gather occasional test results from my tier-2 machines here. I am used to it, but others would most likely be confused.)