Hello everyone, did you guys miss me? :)
I'm back from vacation and I'm catching up with what happened last week.
I did read the 'Monday Virt Test Drama' thread and would like to thank
you guys to handle things promptly. Some thoughts about how to handle
updating the development branches:
1) Everybody makes mistakes, so don't worry too much about it, take your
lesson from it and move on.
2) I recommended using the check_patch.py script to handle the 'merge
pull requests' flow, but I'm OK with the 'Pressing The Green Button'
approach, really, so keep rolling.
3) About non fast forward updates, they have to be done from time to
time (some bad patch that introduced a bug will have to be pulled out).
I don't think I should be the only one doing them, but it is important to:
* Double or triple check what you are doing, normally this is not
necessary. If it's a routine patch you're applying that's not applying
cleanly, then obviously your next is outdated and you have to update it
before pushing things.
* If it really comes down to a non-ff update, announce on the mailing
list you had to do it and why. I think the main case where we want to do
it is to pull off bad patches from next, perhaps *only* in that case.
I'm going to update the maintenance notes
https://github.com/autotest/autotest/wiki/MaintenanceDocs
With these remarks.
Cheers,
Lucas
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
