Auto-tools/Automation Development/Meetings/131216: Difference between revisions

Auto-tools/Automation Development/Meetings/131216 (view source)

577 bytes removed , 17 December 2013

Confirmed users

1,107

edits

@@ Line 12: / Line 12: @@
 = Last Weeks Action Items =
 * {{prev|}} [Andrei] Check Mozmill Automation how Mercurial returns the exit code  for all platforms in case 'hg pull' fails (see github mozmill-ci issue  under blockers)
-** mercurial should only return 0 for success and 1 for failure
-** I have however found a few occurrences in its source code that it might:
-*** when using graft (aka cherry-pick or backport) we might return -1 http://selenic.com/hg/file/1c92524c37cd/mercurial/commands.py#l2998
-*** when attempting a push, we might return 2 http://selenic.com/hg/file/1c92524c37cd/mercurial/commands.py#l4715
-** I don't know why we need these. From what I've read we as long as we get 0 we should be fine. Any other return code should be treated as an Error.
-* {{prev|}} [Dave] Look into recording weekly meetings (chase Geo for documentation)
 * {{new|}} [Henrik] Update meeting page for new format
 ** Wiki transition will happen by next year so we will have our last meeting this year in the old format
-* {{new|}} [Dave] Update the 'How to handle a meeting' wiki page for recording and publishing the video
+* {{new|}} [Henrik] Update the 'How to handle a meeting' wiki page for recording and publishing the video
+* {{new|}} [Henrik] Start recording the meeting
 = Highlights =