The Geode 1.9.0 release includes a source-only release of the geode-native
repo. There's a pull-request in process to update version numbers and the
doc build environment in that repo; should be ready to merge tomorrow
morning.
On Tue, Mar 19, 2019 at 5:20 PM Dale Emery wrote:
> The Micrometer A
The Micrometer API is in, and marked as experimental. But we have not yet
updated CacheFactory to allow injecting a meter registry (or metrics publishing
service) there. So currently the only way to publish is to add metrics
publishing service via the ServiceLoader mechanism.
—
Dale Emery
dem..
Manageability just yesterday moved all work-in-progress behind a feature flag;
yes, we are comfortable releasing in the current state.
> On Mar 19, 2019, at 3:29 PM, Dan Smith wrote:
>
> Is the geode-managability sub-project and the new micrometer API in a place
> where we can cut a release
Is the geode-managability sub-project and the new micrometer API in a place
where we can cut a release branch? I know a bunch of changes have gone in
since the release branch, are we comfortable releasing these new
experimental features as they are right now?
-Dan
On Tue, Mar 19, 2019 at 2:38 PM
+1. We want to ship with confidence and we have more trust in develop right
now.
On Tue, Mar 19, 2019 at 2:11 PM Dick Cavender wrote:
> +1 to re-cutting the 1.9 release branch off a more stable develop sha
> within the last couple days.
>
> On Tue, Mar 19, 2019 at 1:14 PM Bruce Schuchardt
> wro
+1 to re-cut.
-Anil.
On Tue, Mar 19, 2019 at 2:11 PM Dick Cavender wrote:
> +1 to re-cutting the 1.9 release branch off a more stable develop sha
> within the last couple days.
>
> On Tue, Mar 19, 2019 at 1:14 PM Bruce Schuchardt
> wrote:
>
> > If we recut the release branch we need to update
+1 to re-cutting the 1.9 release branch off a more stable develop sha
within the last couple days.
On Tue, Mar 19, 2019 at 1:14 PM Bruce Schuchardt
wrote:
> If we recut the release branch we need to update JIRA tickets marked
> fixed in 1.10
>
> On 3/19/19 12:48 PM, Sai Boorlagadda wrote:
> > >
If we recut the release branch we need to update JIRA tickets marked
fixed in 1.10
On 3/19/19 12:48 PM, Sai Boorlagadda wrote:
> It was known at the time that develop was not as stable as desired,
so we planned to cherry-pick fixes from develop until the release
branch was stable enough to shi
> It was known at the time that develop was not as stable as desired, so we
planned to cherry-pick fixes from develop until the release branch was
stable enough to ship.
I want to clarify that we decided to cut the release branch not that
develop was not stable. But really that it is desirable to c
