René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ACTION REQUIRED: workflow change for merging changes to nodejs/node","articleBody":"Based on previous discussion, feedback, and the approval by the TSC (https://github.com/nodejs/node/issues/2434), we are adopting a new workflow for merging pull request in nodejs/node, and making any changes to the code branches at nodejs/node in general. The new workflow needs to be adopted by all @nodejs/collaborators for all changes to be merged to nodejs/node, starting this coming **Monday at 2pm UTC**: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Start+merging+changes+to+nodejs%2Fnode+with+Jenkins\u0026iso=20150831T14\u0026p1=1440\n\nFrom that time on, please refrain from pushing changes to nodejs/node manually, and instead use the workflow documented at https://github.com/nodejs/node/wiki/Merging-pull-requests-with-Jenkins. I also added a wiki page specifically on [how to deal with flaky tests](https://github.com/nodejs/node/wiki/Flaky-tests). \n\nThe workflow for testing (but not landing) pull requests with Jenkins is unchanged, and now documented here: https://github.com/nodejs/node/wiki/Testing-pull-requests-with-Jenkins\n\nI'll be monitoring Jenkins to make sure things keep working smoothly. Let me and @nodejs/jenkins-admins  know if you encounter any issues with the CI infrastructure or to share your feedback. Thank you!\n","author":{"url":"https://github.com/orangemocha","@type":"Person","name":"orangemocha"},"datePublished":"2015-08-28T14:16:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":76},"url":"https://github.com/2598/node/issues/2598"}