Hi Jinwoo,
Appreciate your support. I am excited to bring Java21/Jakarta to Geode. You
can always create a branch and make changes related to Java21/Jakarta on a
feature branch and then when it is ready we can merge to develop. The prior
process followed so far is git-flow process and versioning/b
I would expect it to succeed too. Looking at the error it seems rat failure
which is licensing header check in each file. It is possible if someone
merged a commit with a new file without a license header.
This fio should have a reference to which all files are violating license
header check.
fil
Bowen wrote:
>
>
> > On Nov 12, 2024, at 2:05 AM, Calvin Kirs wrote:
> >
> > Hi Sai,
> > On Tue, Nov 12, 2024 at 2:28 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com <mailto:sai.boorlaga...@gmail.com>>
> > wrote:
> >
> >> Thanks San
Thank You,
> Sanjay Yadav
>
>
>
> On Tue, Oct 22, 2024 at 11:36 AM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> wrote:
>
> > I suggest we create a jira for specific change so we can track the
> changes.
> > You can request access to jira and create a
wrote:
> Thank you Sai Boorlagadda for guidance, links were super helpful.
>
> I will run all the tests and raise PR if it is small fix, should I use any
> jira as such from my git branch?
>
> Thank You,
> Sanjay Yadav
>
> On Tue, Oct 22, 2024 at 9:00 AM Sai B
Hi Sanjay,
I would like to understand where you are in setup? Are you able to checkout
the code and build?
I would say 'Geode in 5 minutes' is a great start and from there Testing.md
shows how to run each tests, while building.md shows how to setup project
and build in ide such as intellij.
>Fro
I pushed a commit to asf-site and the website is deployed now. Verified new
links are working.
There was a Dockerfile to build using nanoc and then the contents have to
be copied from build folder to the asf-site branch.
Sai
On Fri, Oct 18, 2024, 8:16 AM Drew Foulks wrote:
> I don't think ther
I pushed a commit to asf-site and the website is deployed now. Verified new
links are working.
There was a Dockerfile to build using nanoc and then the contents have to
be copied from build folder to the asf-site branch.
Sai
On Fri, Oct 18, 2024, 8:16 AM Drew Foulks wrote:
> I don't think the
me-ov-file#deploy-the-update
Sai
On Fri, Oct 18, 2024, 6:57 AM Rich Bowen wrote:
>
>
> > On Oct 17, 2024, at 4:13 PM, Sai Boorlagadda
> wrote:
> >
> > Thanks Rick,
> >
> > I will be able to approve later tonight.
>
> Thanks Sai. I see that it was mer
Thanks Rick,
I will be able to approve later tonight.
Sai
On Thu, Oct 17, 2024, 12:55 PM Rich Bowen wrote:
> https://github.com/apache/geode-site/pull/22
>
> When we were talking with our new friends from SAS last week, it was
> mentioned that the links to the mailing list archives on
> https:
+1 for moving to attic.
Sai
On Fri, Jul 26, 2024, 5:05 PM Mark Bretl wrote:
> Hello Geode PMC and Dev Community,
>
> Based on the minimal responses we have had with requests for new volunteers
> and various discussions on the overall project health, the time has come to
> have a vote for moving
k
>
> On Wed, Jul 19, 2023 at 3:08 PM Mark Bretl wrote:
>
> > Thanks for the update Sai. Your work is much appreciated!
> >
> > --Mark
> >
> > On Wed, Jul 12, 2023 at 9:02 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com
> > >
> > wrote:
Oliver,
Thanks a lot for your contribution and nudging us on the email, we aren't
been active. I will review it soon and get back to you.
Geode is actively seeking contributors and would love to have you and your
colleagues start contributing.
If it's possible, could you outline what are the top
I found out that the infra team is working actively on providing larger
instances for jobs in Github actions. I will resume my work as soon I see
they have an option.
Other than that I couldn't keep up contributing to this project in the last
few weeks.
Sai
Thanks, Mark, looks good to me.
Sai
On Mon, 8 May 2023 at 13:48, Mark Bretl wrote:
> Here is the draft of the board report for the month of May 2023, I will
> submit to the board on Wednesday, May 10
>
> ## Description:
> The mission of Apache Geode is the creation and maintenance of software
>
> Sai,
>
> Do you have an INFRA Jira ticket?
>
> --Mark
>
> On Tue, May 2, 2023 at 9:53 AM Sai Boorlagadda
> wrote:
>
> > There is no ETA provided.
> >
> > Sai
> >
> > On Sat, 29 Apr 2023 at 14:47, Kirk Lund wrote:
> >
> &
There is no ETA provided.
Sai
On Sat, 29 Apr 2023 at 14:47, Kirk Lund wrote:
> Did INFRA give any hint as to when they might provide the bigger VMs?
>
> On Mon, Apr 17, 2023 at 8:24 PM Sai Boorlagadda >
> wrote:
>
> > I went ahead and merged github workflow job
> -Kirk
>
> On Thu, Apr 13, 2023 at 3:02 PM Kirk Lund wrote:
>
> > Is the coreDistributedTests the only dunit job that currently takes too
> > long? If it is we may want to split that into more than one job.
> >
> > -Kirk
> >
> > On Wed, Apr 12,
All,
There is an upper bound for job execution time on free workers (set to 6
hours max[1]), which can be configured beyond 6hrs with a self-hosted
worker. All of our pipeline jobs are using `--max-workers` to parallelize
gradle tasks but `testMaxParallelForks` is left to default which is (1/4th
o
I have a PR[1] that adds acceptance tests to the pipeline. I would
appreciate a review.
Changes:
1) Needed to upgrade testcontainers to the latest version to overcome the
2GB disk space issue causing containers to fail to start
2) Moved a couple of tests as integration tests as they are polluting
Thanks, Krik. Now we are on to acceptance tests. I got most of it working
except two tests:
StartLocatorJmxSerialFilterAcceptanceTest.
startWithJmxManagerDoesNotConfigureJmxSerialFilter_onJava8
StartServerJmxSerialFilterAcceptanceTest.
startWithJmxManagerDoesNotConfigureJmxSerialFilter_onJava8
On
h race conditions. We didn't end up using that utility as much as I
> thought we might. You could consider just ignoring/deleting that test.
>
> -Dan
> ________
> From: Sai Boorlagadda
> Sent: Tuesday, February 7, 2023 5:56 PM
> To: dev@geode.apache.or
://github.com/apache/geode/actions/runs/4119919022
On Mon, 23 Jan 2023 at 11:05, Sai Boorlagadda
wrote:
> After working through unit tests and the builds are passing. I am working
> on adding an integration step to the build pipeline.
>
> Looks like there are a few (4 tests) faili
, 2023 at 11:57 AM Gavin McDonald
> wrote:
>
> >
> >
> > On 2023/01/23 14:59:56 Sai Boorlagadda wrote:
> > > Thanks Gavin,
> > >
> > > This nightly build has been failing for quite a while. I will see
> > > whats going on.
> > >
to same contents as develop.
>
>
>
> *From: *Sai Boorlagadda
> *Date: *Sunday, January 22, 2023 at 8:30 AM
> *To: *dev@geode.apache.org
> *Subject: *Pullrequest required checks
>
> !! External Email
>
> Could someone have info regarding how the required checks are
Seems like the execute_tests.sh hasn't been updated to remove setting the
environment variables after we removed usage of dockerized tests plugin.
Sai
On Mon, 23 Jan 2023 at 21:49, Sai Boorlagadda
wrote:
> Could someone provide context on how integration & dunit tests are run in
Could someone provide context on how integration & dunit tests are run in
CI?
I remember geode had dockerized test plugin that isolates test execution.
But looking at this PR[1] it seems we removed usage of that plugin and have
a customized mechanism to allocate ports so that we don't need to run
ks and
> in your migrate to github actions pr you could change the required checks.
> I would hope this doesn't need a vote as those current required check's
> pipelines seem to all have been removed.
>
> -michael
>
> From: Sai Boorlagadda
After working through unit tests and the builds are passing. I am working
on adding an integration step to the build pipeline.
Looks like there are a few (4 tests) failing[1] on the integration suite.
Let me know if anyone interested to look into them. It would really good to
get integration tests
Thanks Gavin,
This nightly build has been failing for quite a while. I will see
whats going on.
Devs, Do we know about this nightly build? Any info on the setup and how it
is configured?
Sai
On Mon, 23 Jan 2023 at 00:58, Gavin McDonald wrote:
> Hi All,
>
> https://ci2.apache.org/#/builders/72
Could someone review and approve this PR?
https://github.com/apache/geode-benchmarks/pull/170/files
Sai
Could some one explain me what is this gradle task requirement?
I see that we are running this japicmp only for JDK 11. Does it build using
11?
Sai
All,
I would appreciate a review of this PR[1] that adds a GitHub action
workflow to build and unit test develop and runs it on every PR to develop.
This is just the beginning of this migration work and we would like to
merge it as soon as possible.
Will follow up with apiCheck and adding window
Could someone have info regarding how the required checks are enabled on a
Pull Request?
In the process of setting up the Github Actions, I see there are still
Concourse CI checks as "required" eg: on this PR[1]
[1] https://github.com/apache/geode/pull/7870
Thanks
Sai
Seems like there are some environmental-related differences.
On Thu, 8 Dec 2022 at 18:56, Sai Boorlagadda
wrote:
> Kirk,
>
> I updated the github pipeline[1] to run unit tests across multiple JDK
> implementations on the different OS to figure out if there are any JDK/OS
> differ
; Cheers,
> Kirk
>
> On Fri, Dec 2, 2022 at 12:58 PM Kirk Lund wrote:
>
>> Sai, I'll be able to spend some time this weekend on these failing tests.
>> Hope to have some more news to share soon!
>>
>> -Kirk
>>
>> On Mon, Nov 21, 2022 at 4:35 PM Sai
hat the issue was with OpenJDK 8 so we can
> > figure out what to do about it.
> >
> > On Mon, Nov 21, 2022 at 3:29 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
> >
> >> Hello devs,
> >>
> >> I started a parallel act
t I'd be happy to get on some
> sort of zoom or google or other screen sharing conference call to offer
> what little help I can.
>
> -Kirk
>
> On Tue, Nov 15, 2022 at 2:19 PM Sai Boorlagadda >
> wrote:
>
> > Thanks Mark.
> >
> > Dan added me requir
Hello devs,
I started a parallel activity to tease out CI work on using ASF jenkins and
also Github actions (though GHA has several issues). I wanted to provide
some updates on these efforts and seek if others are interested to
collaborate.
Jenkins - Was waiting for INFRA to create a high level f
ode
> > > repository. Still, it remains to be seen, since resource requirements
> on
> > > that repository are really high.
> > >
> > > Sorry I couldn't be of more help, but at least I hope these pointers
> are
> > > useful.
> > >
> &g
Dan,
Could you add me to this ldap group 'hudson-jobadmin' to get administrative
account for Jenkins?
[1]
https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=65147535#Jenkins-HowdoIgetanaccount
?
Sai
On Sat, Nov 12, 2022, 7:33 AM Sai Boorlagadda
wrote:
> Than
ts on
> that repository are really high.
>
> Sorry I couldn't be of more help, but at least I hope these pointers are
> useful.
>
> /Mario
>
>
> From: Niall Pemberton
> Sent: Saturday, November 12, 2022 10:46 AM
> To: dev@geode.ap
Hello Devs,
I would like to understand some of the top priority items that we should
focus and spend our time on while we ramp up with new community members.
Any pointers to the scope of the next release or a list of items we should
do as part of this transition. While going through the mailing l
Devs,
I came across Cloudburst paper which introduces function execution
integrated into a KV store (Anna) by Berkley folks @ RISELabs which
resembles Geode's functions execution engine.
I thought I would share this paper with the rest of the community.
https://arxiv.org/pdf/2001.04592.pdf
Sai
> if one gw receiver stops, the locator will publish to any remote locator
that there are no receivers up.
I am not sure if locators proactively update remote locators about change
in receivers list rather I think the senders figures this out on connection
issues.
But I see the problem that local-
Hello Mario,
I would like to see if having a custom security provider allows you to
configure the default SSL context to set the SNI?
>From your proposal, I see that you have implemented a Java Security
Provider to provide custom KeyManager implementation which distinguishes
certificate based on
+1 for getting this into 1.10
On Thu, Aug 8, 2019 at 11:29 AM Juan José Ramos wrote:
> I'd like to propose including the fix for *GEODE-7022 [1]* in release
> 1.10.0.
> The fix basically improves our own implementation of the
> *RMIClientSocketFactory* to fully support the GEODE SSL settings, al
Building/Rebuilding in IntelliJ fails with error "Cannot start compilation:
the output path is not specified for modules". Any help would be
appreciated. I have been following BUILDING.md[1] to setup intellij.
[1] https://github.com/apache/geode/blob/develop/BUILDING.md
Anthony Baker wrote:
> FYI, I reviewed the geode, geode-examples, and geode-native bits. No
> issues so far (except as noted by Bruce).
>
> Anthony
>
>
> > On Apr 16, 2019, at 1:19 PM, Sai Boorlagadda
> wrote:
> >
> > Thanks Bruce. You can -1 this release cand
That's probably something
> we should fix for 1.9. The code in question was heavily modified for
> this release.
>
> On 4/15/19 3:06 PM, Sai Boorlagadda wrote:
> > Hello, Geode dev community,
> >
> >
> > This is the second release candidate for Apache
0.RC3 -PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1053 build
runAll
PS: I have cherry-picked a commit to fix GEODE-3948
Regards,
Sai Boorlagadda
gt;> * What went wrong:
> >> Execution failed for task ':geode-assembly:signDistTar'.
> >>> Cannot perform signing task ':geode-assembly:signDistTar' because it
> has
> >> no configured signatory
> >>
> >> * Try:
> &g
I did build an RC2 and uploaded to distro.
Sai
On Fri, Apr 12, 2019 at 4:21 PM Bruce Schuchardt
wrote:
> I'm pushing the fix for GEODE-3948 right now. Can you get that into the
> new RC? It was reported on geode-user this week.
>
> On 4/12/19 3:27 PM, Sai Boorlagadda wrote
0.RC2 -PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1052 build
runAll
Regards,
Sai Boorlagadda
ll not be able to build the user guide from sources without
> this change.
> Should be:
>
> ```
>
> rewrite '/', '/docs/guide/19/about_geode.html'
>
> rewrite '/index.html', '/docs/guide/19/about_geode.html'
>
> ```
>
> On
0.RC1 -PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1051
build runAll
Regards
Sai Boorlagadda
ease.
> >
> > On Mon, Apr 8, 2019 at 9:27 AM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
> >
> >> Hello,
> >>
> >> It looks like we have fixed required licensing and bom related issues
> and
> >> the pipeline is l
Hello,
It looks like we have fixed required licensing and bom related issues and
the pipeline is looking much stable with other issues that have been fixed
in last couple of weeks after we have re-cut the branch.
So I wanted to ask the developers to see if we are ready for building an
RC? Are the
der jar in case of Reconnect" be included in 1.9 if
> possible.
>
> Thanks
> --Jens
>
> On Thu, Mar 28, 2019 at 6:50 AM Sai Boorlagadda >
> wrote:
>
> > Changes to LICENSE and NOTICE files are cherry-picked on to release/1.9.0
> > branch.
> >
>
> bad pun).
>
> Anthony
>
>
> > On Mar 15, 2019, at 11:07 AM, Sai Boorlagadda
> wrote:
> >
> > I have a PR[1] to include LICENSE and NOTICE changes to develop.
> > Once I have merged this to develop then I will cherry-pick this onto
> 1.9.0
> > re
I have updated JIRA tickets to 1.9.0 as in "update fixVersion = '1.9.0'
where fixVersion = '1.10.0' AND status in (closed, resolved)"
On Mon, Mar 25, 2019 at 8:49 AM Sai Boorlagadda
wrote:
> Hello Everyone,
>
> As discussed in other email thread I have re
Hello Everyone,
As discussed in other email thread I have re-cut a new release branch
for Apache Geode 1.9.0 - "release/1.9.0" off of sha
"ec5a24b78c51b6a29b8bf656f91004d09510d244".
We already have an existing pipeline for 1.9.0[1], So I will rename
the current release branch as "release/1.9.0-o
he 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)
>>>>>
> >>>>>>> On Mar 19, 2019, at 3:29 PM, Dan Smith wrote:
> >>>>>>>
> >>>>>>> Is the geode-managability sub-project and the new micrometer API
> >> in
> >>>> a
> >>>>>>
> 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
I have a PR[1] to include LICENSE and NOTICE changes to develop.
Once I have merged this to develop then I will cherry-pick this onto 1.9.0
release branch.
[1] https://github.com/apache/geode/pull/3313
On Wed, Feb 27, 2019 at 5:32 PM Anthony Baker wrote:
> I was reviewing the release branch and
> Author: Bruce Schuchardt
> Date: Mon Mar 4 11:39:32 2019 -0800
>
> GEODE-2059 client SSL handshake attempts do not time out
>
> Updating tests to allow an SSLException with cause
> SocketTimeoutException.
>
>
> On 3/4/19 10:12 AM, Sai
I see integration tests are failing on develop. Is there anyone working on
it?
This is failing on release branch too, so I would want to chery-pick if
there is a fix.
Sai
I started working on LICENSE issues.
On Fri, Mar 1, 2019 at 3:55 PM Anthony Baker wrote:
> I’ll point out that the license issue I mentioned earlier this week isn’t
> resolved. And that we’re bundling potentially incompatible Jackson jars.
>
> Anthony
>
>
> > On Mar 1, 2019, at 3:41 PM, Alexand
I am aligned here that we should not be firm on a date be flexible to get a
more stable release out.
But could someone explain to me how would we measure this stability? The
pipelines are green
and the community members have cherry-picked all issues that were critical.
Unless we have some process
+1
On Thu, Feb 28, 2019 at 6:25 PM Owen Nichols wrote:
> This would eliminate a lot of noise from Windows tests, any objection to
> cherry-picking it to release/1.9.0?
>
> This is a test-only change.
>
> Thanks,
> -Owen
+1 for merging this fix to release/1.9.0 as this is required for the
NIO related changes that are already merged.
On Thu, Feb 28, 2019 at 4:47 PM Bruce Schuchardt
wrote:
> This is another ticket associated with the SSL/NIO work that is already
> in release/1.9.0
>
> commit 6d1d82a15a5c548b2aafef
This is a change to windows packer image to use a pinned version of OpenSSH
to 7.2.2.1 as the newer version caused the ssh session to not be terminated
even after the gradle completes successfully leading the actual CI job to
timeout[1].
We never had a green run of *IntegrationTest jobs on windows
By end of this week, I am planning to create the first release candidate.
Are there any other issues other than this last one?
- GEODE-6359 - Bruce is looking into it.
- geode-examples using https in build scripts.
There are about 6[1] issues in JIRA that are in open/in-progress/re-opened
status
FYI all. GEODE-6338 is already on the release branch.
Thanks, Bruce for the update.
https://issues.apache.org/jira/browse/GEODE-6338
On Wed, Feb 27, 2019 at 10:10 AM Anthony Baker wrote:
> Sorry I meant GEODE-6338.
>
> > On Feb 27, 2019, at 9:41 AM, Sai Boorlagadda
> wrote:
Are you asking about GEODE-6343?
Sai
On Wed, Feb 27, 2019 at 7:51 AM Anthony Baker wrote:
> Cool! Is GEODE-63438 also important to fix and merge into 1.9.0?
>
> Anthony
>
>
> > On Feb 22, 2019, at 9:01 AM, Bruce Schuchardt
> wrote:
> >
> > This issue has been resolved on develop and release/1
you like me to?
>
> Thanks,
> -Jason
>
> On Thu, Feb 21, 2019 at 3:37 PM Sai Boorlagadda >
> wrote:
>
> > GEODE-6359 is unassigned in JIRA. Who is working on it?
> >
> > On Wed, Feb 20, 2019 at 9:08 AM Jason Huynh wrote:
> >
> > > Oh ok I thou
I fixed the build. My apologies I didn't rebase before merging my PR.
On Tue, Feb 26, 2019 at 12:33 PM Sai Boorlagadda
wrote:
> My commit broke the build on develop. I am on it.
>
>
My commit broke the build on develop. I am on it.
concurrent access and modification of
> gauge statistics.
>
> ~Helena
>
> On Wed, Feb 20, 2019 at 3:58 PM Jacob Barrett wrote:
>
> > My bad! Sorry!
> >
> > > On Feb 20, 2019, at 3:22 PM, Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
>
issues.apache.org/jira/browse/GEODE-6359 This
> seems like a bad thing to have in the product. It looks like a possible
> issue when processLeaveRequests. I think the fix would be to just copy the
> list or not log the list of members.
>
>
>
> On Tue, Feb 19, 2019 at 5:35 PM S
6359
> This
> > seems like a bad thing to have in the product. It looks like a possible
> > issue when processLeaveRequests. I think the fix would be to just copy
> the
> > list or not log the list of members.
> >
> >
> >
> > On Tue, Feb 19, 2019 at 5:
Jake,
release branch build seems broken due to spotless changes.
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-0-main
Sai
On Wed, Feb 20, 2019 at 2:59 PM Jacob Barrett wrote:
> Done!
>
> > On Feb 20, 2019, at 1:22 PM, Udo Kohlmeyer wrote:
> >
> > +1, Go,Go,GO!
Do we need to create an infra ticket to create a new release?
I don't seem to have permissions to create releases in Jira.
On Wed, Feb 20, 2019 at 8:42 AM Jacob Barrett wrote:
> Release manager need to add the next version number to JIRA when they
> branch the release. Changes going into develop
NPE that occurs
> > when we process leave requests.
> >
> >
> >
> > On Tue, Feb 19, 2019 at 2:25 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
> >
> >> My earlier release branch has created as 'release/1.9' without the p
I am on it.
On Tue, Feb 19, 2019 at 2:25 PM Sai Boorlagadda
wrote:
> Hello Geode Dev Community,
>
> As we have created a release branch for Apache Geode 1.9.0 - "release/1.9.0"
> please create a CI pipeline for running tests on this branch.
>
> Regards
> Sai
>
>
I am in process of adding a new ordinal for 1.10.0 and see that currently
the variables are named as GEODE_XYZ for a release x.y.x (eg, private
static final byte GEODE_1100_ORDINAL = 105;)
Question is are there any side effects for naming it as GEODE_1100_ORDINAL
for 1.10.0?
Not sure if there is a
My earlier release branch has created as 'release/1.9' without the patch
number in semver.
So I have re-created a new release branch 'release/1.9.0'.
I will go ahead delete the unwanted branch 'release/1.9'
Sai
On Tue, Feb 19, 2019 at 2:17 PM Sai Boorlagadda
wr
Hello Geode Dev Community,
As we have created a release branch for Apache Geode 1.9.0 - "release/1.9.0"
please create a CI pipeline for running tests on this branch.
Regards
Sai
cluding a distributed deadlock.
>
> On 2/15/19 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]
> >
Hello Everyone,
As discussed in my earlier email I have created a new release branch
for Apache Geode 1.9.0 - "release/1.9"
Please do review and raise any concern with the release branch.
If no concerns are raised, we will start with the voting for the
release candidate soon.
Regards
Sai
%20Reopened)%20AND%20fixVersion%20%3D%201.9.0
Sai
On Fri, Feb 15, 2019 at 12:56 PM Sai Boorlagadda
wrote:
> 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?
>
&
detection so they've
> > needed extensive testing.
> >
> > On 2/15/19 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.
>
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 sh
1 PM Sai Boorlagadda
wrote:
> I didn't mean blocking a release but the release process (including
> cutting the branch).
>
>
> I thought there was a consensus about strictly cutting a
>
> branch[1] with our new fixed minor release cadence and
>
> only allow crit
, Feb 14, 2019 at 12:00 PM Nabarun Nag wrote:
> I could not find any DISCUSS mails about not blocking a release. I may be
> wrong, I apologize for that but could point me to the mail / documentation
> about the release management.
>
> Regards
> Naba
>
> On Thu, Feb 14, 201
> On Thu, Feb 14, 2019 at 10:32 AM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> wrote:
>
> > I volunteer to be the release manager for 1.9.
> >
> > Sai
> >
> > On Wed, Feb 13, 2019 at 7:48 PM Alexander Murmann
> > wrote:
> >
> >
I volunteer to be the release manager for 1.9.
Sai
On Wed, Feb 13, 2019 at 7:48 PM Alexander Murmann
wrote:
> If there are no other takers, I can act as release manager for 1.9 and will
> cut a release branch this week.
>
>
> On Tue, Jan 29, 2019 at 1:50 PM Alexander Murmann
> wrote:
>
> > Hi
Thanks Naba. I couldn't get this test to pass.
Anyways if it still counts +1 for the release. I am okay to release native
code if the version doesn't default to 1.8.0 as we are not including
binaries.
Sai
On Tue, Dec 11, 2018 at 7:15 AM Jacob Barrett wrote:
> The java bits generate a property
-0
- Ran examples
- Building geode from source distribution or release branch consistently
fails 1 unit test
org.apache.geode.internal.cache.partitioned.rebalance.PartitionedRegionLoadModelJUnitTest
> testRedundancySatisfactionPreferRemoteIp FAILED
As CI is green on unit tests, I am considering t
1 - 100 of 189 matches
Mail list logo
