Hello all,

All of you are aware that we have decided to release sentry 2.0.0. As a
first step I propose the cut the branch for sentry 2.0.0 off the master
today.
We still have couple of issues that are pending to for  2.0.0 but I would
like to cut it as the tests on the master have become flaky.
Here are jira's that are blocking sentry 2.0.0 release


   - *Solr*


   1. SENTRY-2042  Support file based Sentry provider for Solr plugin
      2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry permissions




* - Hive *

   1. SENTRY-1640 Implement HMS Notification barrier on the HMS plugin side
      2. SENTRY-2048 Bump Hive version to 2.3.2

If we cut the branch, we can limit commits to sentry 2.0.0 to that are
needed and isolate the root cause for the test failures and stabilize 2.0.0
branch.

-Kalyan

Reply via email to