Just tag, I think.
On Fri, Feb 15, 2019 at 2:15 PM Sai Boorlagadda
wrote:
> There are about 8[1] issues in JIRA that are in open/in-progress/re-opened
> status for 1.9.0.
> Can I request all the devs to reflect JIRA with current status?
>
> [1]
> https://issues.apache.org/jira/browse/GEODE-6107?
There are about 8[1] issues in JIRA that are in open/in-progress/re-opened
status for 1.9.0.
Can I request all the devs to reflect JIRA with current status?
[1]
https://issues.apache.org/jira/browse/GEODE-6107?jql=project%20%3D%20GEODE%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reop
Thanks Dave. I keep a note to include Geode Native.
As we are including only a source release for Geode Native
do we need to create a release branch? Or just tag it?
Though we will eventually be tagging Geode & Geode Examples repos.
So until it gets released I think as a place holder I can go ahe
Sai,
The Geode 1.8 release included (for the first time) a source snapshot of
the geode-native repo.
As far as I know, the same treatment would be in order for v1.9.
On Fri, Feb 15, 2019 at 9:01 AM Bruce Schuchardt
wrote:
> I would like to get GEODE-6369 into the next release but that can be
>
I would like to get GEODE-6369 into the next release but that can be
done in a cherry-pick after I finish testing. The changes are in in
discovery, joining the cluster and in failure detection so they've
needed extensive testing.
On 2/15/19 7:53 AM, Sai Boorlagadda wrote:
I am planning to cu
I have merged https://github.com/apache/geode/pull/3195 just now.
-michael
On Fri, Feb 15, 2019 at 8:27 AM Sai Boorlagadda
wrote:
> BTW, Is PR #3195 is planned to merge today?
>
> On Fri, Feb 15, 2019 at 7:53 AM Sai Boorlagadda >
> wrote:
>
> > I am planning to cut the1.9 release branch today
BTW, Is PR #3195 is planned to merge today?
On Fri, Feb 15, 2019 at 7:53 AM Sai Boorlagadda
wrote:
> I am planning to cut the1.9 release branch today after merging this
> PR #3195 which is reverting changes to GEODE-6334 & GEODE-6345.
>
> Is there anything other than that I should be aware of?
>
I am planning to cut the1.9 release branch today after merging this
PR #3195 which is reverting changes to GEODE-6334 & GEODE-6345.
Is there anything other than that I should be aware of?
Here is the list of issues that were requested to be included into 1.9.
If there is any plan to merge any of
