Christopher Nielsen

> @mascguy I'm going to ask you to remove your lock on this unless you're willing to finish it in the next few days. Please let other people finish the...

> I rebased onto `HEAD` and did a push. I made minor changes, e.g. not deleting `py27-protobuf3`. Besides that, I didn't spend any time looking at if this works or...

Added @jmroot, @ryandesign, and @neverpanic for thoughts/feedback. (Particularly related to what details we include - or don't include - for `extract.post_args`.)

> I think we should include a paragraph describing what the `extract.post_args` line does, rather than the full invocation, which is indeed quite complicated. Sounds good, I'll try to get...

> > I think we should include a paragraph describing what the `extract.post_args` line does, rather than the full invocation, which is indeed quite complicated. > > Sounds good, I'll...

Merging these changes in their current state. We'll have time to refine before the next release, if anyone would like to see further changes/additions. Feedback welcome and appreciated, as always.

I'd prefer that we have a 3rd status - like "not supported," or something akin to that - to differentiate from a simple success/failure. Anyone else... thoughts?

Similarly, if there was at least one build failure prior to setting `known_fail`, that will also be in effect. And that can be a bit frustrating, when drilling down the...

I'd also add: Don't show deleted subports, on the parent port's detail screen.

While this sounds great in principle, tracking deleted ports indefinitely isn't ideal either. Has there been any thought/discussion, related to purging that info? My vote would be that we remove...