Do I have terrible timing when it comes to landing patches, or has
inbound been closed due to bustage far too often over the past couple of
months? At first I thought maybe it was the former, but now I'm
believing that it is the latter.
As of late, when I check to see if inbound is open, I jus
I think perhaps part of the question is what the purpose of m-i versus try
is.
My general algorithm is that you should get your patch to the point
where you have tested it locally and have reasonable confidence that there
are no portability issues and then it's fine to land it on m-i without try.
Some exciting statistics on these things if you're interested:
http://futurama.theautomatedtester.co.uk/
I'll leave it to you to draw whatever conclusions you want.
-Ryan
On 4/20/2015 4:54 PM, Aaron Klotz wrote:
Do I have terrible timing when it comes to landing patches, or has
inbound been cl
"then it's fine to land it on m-i without try."
Maybe because I usually work on core, and such confidence is hard to reach
there, but I'd like to think at least a try run that check if the patch
builds on all platform and a full test run on at least one platform is not
too much sacrifice of ones t
4 matches
Mail list logo
