On 11/11/17 11:47 AM, Jed Brown wrote:
The way I see it - a broken next [where folks can't easily figure out
who or which commit is responsible for the brakages] - doesn't help
much..
The fundamental problem here is that we aren't accurate enough at
placing blame and getting the appropriate person to fix it. It doesn't
help that we are a distributed team and have plenty of our own
obligations. I can't fix something while I'm teaching class or meeting
with students, for example. But we should all be able to get to it
within a day, either to withdraw the branch from 'next' or to actually
fix it.
I think a lot of our noise in 'next' is "stupid shit", like compilation
failing on some architecture. Automating a very limited test suite
running on PRs within minutes should help a lot to deal with that. More
subtle interaction problems can and should continue to be dealt with via
'next'.
I agree with both points here which is why I created
bin/maint/exampleslog.py which is now in master but not
hooked up in runhtml.py or linked to from the nightlies.
The idea of this is that it assigns responsibility
by the last committer of a given example. While this is
obviously not perfect, if someone edited an example recently,
they are in the best position to take a quick look at what
the problem is (hence, saying it assigns responsibility and
not blame since you don't know where the blame lies).
This would allow a distribution of responsibility rather than just
having a single person have to do everything, and doesn't require
a huge paradigm shift.
Scott
--
Tech-X Corporation kru...@txcorp.com
5621 Arapahoe Ave, Suite A Phone: (720) 974-1841
Boulder, CO 80303 Fax: (303) 448-7756
