..today including an important decision regarding Python versions and Buildbot master!
1. *Introduction* (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-11>, 16:34:33) 2. *Development week-in-review* (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-13>, 16:35:00) 1. We have a healthy number of PRs, both bug fixes and contributed enhancements (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-24>, 16:37:34) 2. lots of improvements are to nine features, so it is gaining momentum (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-28>, 16:38:14) 3. *AGREED*: will release beta9 on Monday, potentially without buildbot-worker (like beta8) (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-46>, 16:42:04) 3. *service2.buildbot.net <http://service2.buildbot.net> downtime* ( djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-52>, 16:42:53) 1. One of our three servers failed on Friday, and Amar brought it back up on Monday (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-53>, 16:43:07) 2. Some work nearby in OSUOSL dislodged its power cable, and the monitoring didn't alert Amar (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-54>, 16:43:32) 3. https://www.statuspage.io/pricing ? (sa2ajj <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-65>, 16:45:14) 4. *AGREED*: will set up uptimerobot.com to alert us of failures like this more quickly in the future (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-89>, 16:49:34) 4. *Bug 2340 Update* (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-94>, 16:51:26) 1. removed usePTY worker-side configuration option (PR 2184) (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-134>, 16:58:28) 2. planning to have a release-able buildbot-worker this week, after which we can make a release candidate (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-136>, 16:58:57) 5. *Dropping Python 2.6* (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-156>, 17:04:31) 1. Proposal is to drop master-side support for Python-2.6 (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-158>, 17:04:48) 2. pros/cons assembled before the meeting - https://pastebin.mozilla.org/8869523 (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-162>, 17:05:58) 3. https://fr.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#RHEL_5 ( tardyp <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-168>, 17:08:37) 4. https://github.com/buildbot/botherders/blob/master/policies/support.md (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-189>, 17:13:05) 5. *AGREED*: Buildbot will drop Python-2.6 support with the 0.9.0 release (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-229>, 17:24:44) 6. (see chat log for details of the decision) (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-231>, 17:24:51) 6. *E2E / Integration Testing* (djmitche <https://supybot.buildbot.net/meetings/buildbot/2016/buildbot.2016-05-03-16.33.log.html#l-269>, 17:33:34)
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users