events.action: opened
events.author: GoelDeepak
events.text: ## High Level Description
  
  This is for my own project and this PR is never intended to be merged. I will close when my experimentation is over
  
  ## Related Issues
  
    - [DCOS_OSS-<number>](https://jira.dcos.io/browse/DCOS_OSS-<number>) Foo the Bar so it stops Bazzing.
    - [DCOS-<number>](https://jira.mesosphere.com/browse/DCOS-<number>) Foo the Bar so it stops Bazzing.
  
  ## Checklist for all PR's
  
    - [ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
    - [ ] Read the [DC/OS contributing guidelines](https://github.com/dcos/dcos/blob/master/contributing.md)
    - [ ] Followed relevant code rules [Rules for Packages and Systemd](https://github.com/dcos/dcos/tree/master/docs)
  
  ## Checklist for component/package updates:
  
  If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath `packages`), then in addition to the above please also include:
  
    - [ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): [example](https://github.com/dcos/dcos-mesos-modules/compare/f6fa27d7c40f4207ba3bb2274e2cfe79b62a395a...6660b90fbbf69a15ef46d0184e36755881d6a5ae)
    - [ ] Test Results: [link to CI job test results for component]
    - [ ] Code Coverage (if available): [link to code coverage report]
  ___
  **PLEASE FILL IN THE TEMPLATE ABOVE** / **DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE**
  
  ## Instructions and Review Process
  
  **What is the review process and when will my changes land?**
  
  All PRs require 2 approvals using github's [pull request reviews](https://help.github.com/articles/about-pull-request-reviews/).
  
  Reviewers should be:
  * Developers who understand the code being modified.
  * Developers responsible for code that interacts with or depends on the code being modified.
  
  It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has **2 ship-it's**, **no red reviews**, and **all tests are green** it will be included in the [next train](https://github.com/dcos/dcos/blob/master/contributing.md).
events.title: [WIP] make periodic reconcile of l4lb config
events.type: issue
events.action: created
events.author: spahl
events.text: @mesosphere-mergebot bump-ee
events.type: comment
events.action: created
events.author: GoelDeepak
events.text: @mesosphere-mergebot bump-ee
events.type: comment
data_with_bots.bot: Your pull request's branch is not based on the most recent version of `master`. Please rebase your changes against this repo's `master` branch.
data_with_bots.meta: This message directly preceded comment from bot *mesosphere-mergebot* by author *spahl*:
data_with_bots.text: @mesosphere-mergebot bump-ee
data_with_bots.bot: Enterprise Bump PR: mesosphere/dcos-enterprise/pull/1619
data_with_bots.meta: This message directly preceded comment from bot *mesosphere-mergebot* by author *GoelDeepak*:
data_with_bots.text: @mesosphere-mergebot bump-ee
data_without_bots.meta: This message directly preceded comment from bot *mesosphere-mergebot* by author *spahl*:
data_without_bots.text: @mesosphere-mergebot bump-ee
data_without_bots.meta: This message directly preceded comment from bot *mesosphere-mergebot* by author *GoelDeepak*:
data_without_bots.text: @mesosphere-mergebot bump-ee