What is the problem with ports PR reaction delays?
bright at mu.org
Sun Jan 26 02:05:17 UTC 2014
On 1/25/14 3:41 PM, Yuri wrote:
> On 01/25/2014 14:44, Aryeh Friedman wrote:
>> The key seems to be that no one has time to do the stuff they really
>> to do (get new ports into the system)... to that end automating
>> that can be automated is sure help free up comitter time so they can
>> at what is interesting
> Yes. I just can't imagine any generic port tests that can't be
> automated and coded into the script once and for good.
> Ideal system should be like github with the added automated testing
> between pull request submission and merge. It should either fail and
> notify the submitter, or succeed and notify the committers.
> Today all committers do for ports is running some generic tests by
> hand, like 'lint' with various flags. Install/uninstall/etc. No wonder
> this isn't very a rewarding activity, and committers probably perceive
> it as a necessary evil. The way how it is, it causes a waste of their
More information about the freebsd-ports