I think we should look at other examples of git-flow merge practices for
this kind of thing. We can't be the only project that does this.
But I vote for a merge commit
On Tue, Nov 12, 2019, 16:20 Owen Nichols wrote:
> It’s been a few weeks since 1.9.2 release was announced, and there is
> still
What Owen said basically... I prefer to try for an early date and reschedule to
a later date if I must. Aiming for a later date leaves little window to deal
with surprises other than to miss the target date. Its almost never bad to come
in a few days early, but it is rarely good to come in late.
It’s been a few weeks since 1.9.2 release was announced, and there is still no
record of it on master. What should we do?
A) never record 1.9.2 on master; instead keep the most recent release/1.9.x
branch around indefinitely (normally we delete release branches after pushing
them to master).
B
Could be:
* not very many fixes have come in, so maybe there’s actually nothing further
we’re waiting for?
* to give us a better chance of hitting Dec 2 goal, in case it takes more than
one RC?
* some people might prefer to give feedback against a formal RC rather than
informally against the bra
I think it's really great to agree on the date by which we want to have a
RC1 early. However, I thought the target release date is beginning of
December, which would probably bring us to December 2nd, given the first is
a Sunday. The voting period is 3 days. I would have expected that we'd
create t
+1 for cutting RC1 within two weeks of creating the release branch :)
> On Nov 12, 2019, at 3:00 PM, Mark Hanson wrote:
>
> Hello Geode Dev Community,
>
> We have a release branch for Apache Geode 1.11.0 - “release/1.11.0”. People
> have been voting to pick up fixes and I have been cherry pick
Hello Geode Dev Community,
We have a release branch for Apache Geode 1.11.0 - “release/1.11.0”. People
have been voting to pick up fixes and I have been cherry picking them
accordingly. I think it is important that we look forward to a release date and
I have picked November 19th, 2019 as a tim
update: It is not possible to create the geode-native-build image based on the
geode image. Geode image is based on alpine, and geode-native-build needs Clang
6, which is not available yet for alpine. We will have to wait until it is
released.
De: Alberto Bustama
Good idea Anthony, I will investigate that.
BTW, I have observed that geode/docker/Dockerfile is outdated. It is using "ENV
GEODE_VERSION 1.9.0". I suspect that after the release of 1.10 the changes done
in the Dockerfile were not merged back to develop, maybe the release branch was
not merged
