On Thu, Feb 27, 2014 at 2:02 PM, Bryan Davis bd808@wikimedia.org wrote:
- Cutting the branch should be automatic. Jenkins could do this easily
and make the timing predictable for all parties.
Yeah this is true. Especially since we got rid of wmf-specific hacks in the branch :)
- It seems like the php-1.XwmfY checkouts on tin could be either
shallow or single branch checkouts. I think Chad started playing with having multiple working copies that share the same repository which might be even nicer.
Yeah. I'll start poking this again once I'm back Monday.
- Speaking of Chad's prototype work, /a/common/php-git makes
`updateWikiversions` throw a warning: "updateBitsBranchPointers: link target /usr/local/apache/common-local/php-git/skins does not exist."
Well it shouldn't exist since it's a bare repo ;-) Script needs adjusting.
- I tried to make a script to automate copying security patches from
one branch checkout to the next. It worked sort of. `git apply` wasn't smart enough to figure out that the patches I pulled off of the wmf15 checkout were already applied in the wmf16 branch. It would be nice to figure this out and get it automated or find a better way in general to manage security patches.
Yes. This a thousand times. Let's brainstorm next week :)
- My ssh-agent (OS X 10.8.5) croaked badly when trying to run
sync-wikiversions. This seems to be triggered by the full fanout (not batched) dsh call. Aaron had to step in and run both sync-wikiversions for me.
I've been complaining about this for months. It's one of the reasons I'm pretty convinced Tampa is often horribly out of sync because I imagined I wasn't alone in getting such errors.
Things actually went pretty smoothly though. Thanks a lot to Chad and Sam for helping me make a checklist and Aaron for being around to lend a hand when I fell and couldn't get up.
You're very welcome. Hopefully we can tidy up some of the pain points you mentioned.
-Chad