I'd like to see the changes from
https://issues.apache.org/jira/browse/GEODE-7013 included in the Geode 1.10
release. GEODE-7013's changes restore gfsh help/hint behavior that was lost
during a refactor in the earliest
releases of Geode. The commit occurred after SHA1
dc6890107a2651d8ba1450e8db8a1
> also
> > wonder if that fits our "critical issue" rule for being merged after the
> > branch has been cut or hold up the release. This has been broken since a
> > very long time. Thoughts?
> >
> > On Tue, Jul 30, 2019 at 10:51 AM Karen Miller
> wr
I have (more than once) committed docs changes for typo fixes without
review. I generally label the commits
with a bold "Commit then Review" message. But, I am bringing this up as I
have purposely not followed what
looks to be a positively-received proposed policy, since I have not gotten
reviews
May I have access to concourse.apachegeode-ci.info, so that I can see
details of
of my jobs, and re-trigger failed PR jobs?
Thanks. Karen
Draft board report for November 2019. Submitting in 2 hours! Quick
feedback, please!
## Description:
The mission of Apache Geode is the creation and maintenance of software
related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout
Here's the text of the board report I submitted (November 2019). Thank you
everyone for the quick feedback.
## Description:
The mission of Apache Geode is the creation and maintenance of software related
to a data management platform that provides real-time, consistent access to
data-intensive ap
; +1 LGTM
> >
> > On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote:
> >
> >> Draft board report for November 2019. Submitting in 2 hours! Quick
> >> feedback, please!
> >>
> >> ## Description:
> >> The mission of Apache Geode is t
## Description:
The mission of Apache Geode is the creation and maintenance of software
related to a data management platform that provides real-time, consistent
access to data-intensive applications throughout widely distributed cloud
architectures.
## Issues:
There are no issues requiring board
+1
My vote is only based on running the examples with RC 4. I didn't check
anything else.
On Mon, Dec 23, 2019 at 3:09 PM Aaron Lindsey
wrote:
> The release notes section on the wiki just says "tbd". Also, I cannot find
> Mark’s public key in any of the public PGP key servers (such as
> https:/
Geode Developers,
Here's the start of a board report that is due tomorrow (Feb 12).
I feel that the Project Activity or Community Health section could use more
information
about what we're working on. There are so many developers working on so many
exciting areas that I'm not sure which we all feel
I've submitted our quarterly report. The ASF requests that we no longer
email
the board with the report as part of the process. So, this email is a copy
of the
report that I submitted. Karen
## Description:
Apache Geode is a data management platform that provides a database-like
consistency mod
+1
Karen
On Thu, Apr 23, 2020 at 8:14 AM Dan Smith wrote:
> +1
>
> -Dan
>
> On Thu, Apr 23, 2020, 8:05 AM Anthony Baker wrote:
>
> > Please do, this will match our default approach to development
> > (gitflow-ish).
> >
> > +1
> >
> > Anthony
> >
> >
> > > On Apr 23, 2020, at 7:35 AM, Blake Ben
Apache Geode developers, please thank Dave Barnes for putting together
the May 2020 board report that I filed today. Here is the contents of the
report:
## Description:
The mission of Apache Geode is the creation and maintenance of software
related to a data management platform that provides real
+1 for including this documentation in the 1.13 release
On Wed, May 20, 2020 at 2:31 PM Dave Barnes wrote:
> Edit completed, reviewed, and committed.
>
> +1 for including this in the 1.13 support branch.
>
> On 2020/05/20 16:54:09, Dave Barnes wrote:
> > + 0.5
> > Good material! I'm in favor o
. Fielding
Date: Mon, Aug 3, 2020 at 10:52 AM
Subject: Geode Board Report due by Wed Aug 12nd - Initial Reminder
To: Karen Miller
Cc:
Hello,
According to our records, you are listed as the chair of Geode,
a committee that is due to submit a report by Wed Aug 12nd
for the next ASF board meeting.
Still no volunteers? It is a nice service that you can perform for our
community.
Thanks. Karen
On Tue, Aug 4, 2020 at 9:15 AM Karen Miller wrote:
> Can I get a volunteer to draft our August 2020 report? Doesn't take much
> time. Help is available for the asking if you've
Here's a first draft of a board report. I'd like to include some of the
project's many blog posts (any new videos? did anyone give a Geode talk at
a workshop or conference?) in our Community Health section. Please send me
a link and hopefully an approximate date when the blog was posted.
Please
Thanks, Anthony. Here is Draft 2 of the August board report. Corrections
and comments by Monday at noon please.
## Description:
The mission of Apache Geode is the creation and maintenance of software
related
to a data management platform that provides real-time, consistent access to
data-intensiv
I've filed the August 2020 board report. Thanks for the updates about blogs.
Here is a capture of the report:
## Description:
The mission of Apache Geode is the creation and maintenance of software
related to a data management platform that provides real-time, consistent
access to data-intensive a
27;s focus. Would it be a good idea to add something like this?
- We're actively working on v1.13.1, which will contain many bug fixes.
Since the report is due quite soon, please get corrections/additions
to me before
Tuesday Nov 10 (tomorrow) at 3pm Pacific time.
Thanks.
Karen Miller
I
Here is a copy of the board report submitted today, Tues. Nov 10, 2020.
Karen Miller
I work for VMware.
This email is written in my capacity as Chair of the Apache Geode PMC.
## Description:
The mission of Apache Geode is the creation and maintenance of software related
to a
I've filed the Geode report. Thanks, Dave!
Karen Miller
I work for VMware.
This email is written in my capacity as Chair of the Apache Geode PMC.
On Mon, Feb 8, 2021 at 6:47 PM Dave Barnes wrote:
>
> The numbers come from Apache - I'm not sure how they count 'em up. It w
Let's finish GEODE-2913, the documentation for improvements made to the
Lucene integration and include it with the 1.2.0 release!
On Sun, May 14, 2017 at 6:47 PM, Anthony Baker wrote:
> Hi everyone,
>
> Our last release was v1.1.1 in March. We have made a lot of great
> progress on the develop
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59653/#review176370
---
Ship it!
- Karen Miller
On May 30, 2017, 9:21 p.m., Dave
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59866/#review177130
---
Ship it!
Ship It!
- Karen Miller
On June 6, 2017, 10:50 p.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59923/#review177342
---
Ship it!
Ship It!
- Karen Miller
On June 8, 2017, 5:33 p.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60873/#review180607
---
Ship it!
Ship It!
- Karen Miller
On July 14, 2017, 5:08 p.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60881/#review180608
---
Ship it!
Ship It!
- Karen Miller
On July 14, 2017, 8:02 p.m
A guarded +1 based on limited testing of the RC:
Built the Geode RC from source.
Built and ran the RC (partitioned) geode-example against the Geode RC, which
means I ran gfsh, started a locator and some servers with gfsh, did some
puts and gets via
the API, and ran a query and other commands via g
+1
Ran the 1.2.1 RC4 partitioned geode-example against Geode 1.2.1 RC4. So,
built Geode from
source, built one of the examples, ran gfsh commands to start locator and
servers as well as ran
a query, and did some puts and gets via API.
Also checked that the manual builds and contains 1.2.1 change
Mike,
I've just cherry picked commit SHA1
ac7db5b2950af134233c976b3f63f3e48e8d3fb9 onto the release/1.6.0 branch.
This commit updates the documentation for GEODE-4384. This JIRA ticket
already had its code committed prior to
creation of the release branch, but the JIRA ticket was still unresolved
Geode devs, I think that my merges of commits for GEODE-5071 and
GEODE-5242 really
belong in Geode 1.7. They just missed making it in before the release
branch was cut. I'm going to
cherry pick them into the 1.7 release branch. If anyone disagrees with
this, let's discuss why, and we
can always
+0 for me as well. I had also noted that the documentation has a couple of
prominent
and incorrect instances of 1.0.0-incubating. If there were to be a release
candidate 3,
let's for sure get as many of the incorrect instances of 1.0.0-incubating
fixed as possible.
However, the 2 within the refer
/56626/diff/
Testing
---
Gradle rat check passes. I did not build Geode. I did build the manual, and
no errors occur for a manual build.
Devs with serialization experience should double check that the note changed is
now correct with the package name update.
Thanks,
Karen Miller
s an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56626/#review165417
-------
On Feb. 14, 2017, 12:22 a.m., Karen Miller wrote:
>
> ---
> This
I think that the website content that is currently in geode/geode-site
ought to be moved to its own repository. The driving reason for this is
that changes to the website occur on a different schedule than code
releases. We often want to add a new committer's name or a new
event, and these items
ne by a CI system based on commits. It looks like
> > > some other projects are talking about doing this with jenkins jenkins -
> > see
> > > INFRA-10722 for example.
> > >
> > > -Dan
> > >
> > > On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller
>
Calling all Geode devs:
I've put together a new, and quite basic example that attempts to
demonstrate
what partitioning does. Please review and see the PR at
https://github.com/apache/geode-examples/pull/3
When reviewing this example, please keep in mind that my goal is to
tightly focus on par
It'd be great to get the partitioning example merged in and make the
geode-examples
part of the 1.2.0 release. Everyone take a look at the revised PR:
https://github.com/apache/geode-examples/pull/3
On Mon, Mar 20, 2017 at 3:54 PM, Udo Kohlmeyer
wrote:
> Are there any issues that we can think
or the PMC chair is that the person already be a
Geode PMC member. You are welcome to self-nominate, or to nominate
another person. After nominations have been made, there will be a
separate thread to allow current PMC members to vote on who will
become the new PMC chair.
Thanks.
Karen Miller
---
gradle rat check passes
geode book builds without any broken links
Thanks,
Karen Miller
://reviews.apache.org/r/53971/diff/
Testing
---
gradle rat check passes
geode book builds without any broken links
Thanks,
Karen Miller
fcb792689031c926c51cc6903c33be87388e7e21
geode-docs/reference/topics/elements_ref.html.md.erb
9351bdfc9a74f6808fd87404bbf92577f97458ef
Diff: https://reviews.apache.org/r/54000/diff/
Testing
---
gradle rat check passes
Build of the book finds no broken links.
Thanks,
Karen Miller
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54230/#review157524
---
Ship it!
Ship It!
- Karen Miller
On Dec. 1, 2016, 12:48 a.m
1e75f
Diff: https://reviews.apache.org/r/54266/diff/
Testing
---
gradle rat check passes
The book builds with no broken links.
Thanks,
Karen Miller
check passes
Building the book finds no broken links.
Thanks,
Karen Miller
html.md.erb
(line 191)
<https://reviews.apache.org/r/54332/#comment228667>
Please change java version number here as well.
- Karen Miller
On Dec. 3, 2016, 12:57 a.m., Dave Barnes wrote:
>
> ---
> This is an automatically
hanks,
Karen Miller
2e725a107986f76a621a85bcdd8711e8b56b63a5
Diff: https://reviews.apache.org/r/54499/diff/
Testing
---
Thanks,
Karen Miller
builds with no broken links.
Thanks,
Karen Miller
/data_location_cache_transactions.html.md.erb
d96de82fa7d5f4074c88863c1732363530c12d39
Diff: https://reviews.apache.org/r/54723/diff/
Testing
---
gradle rat check passes
Geode book builds with no broken links
Thanks,
Karen Miller
/data_location_cache_transactions.html.md.erb
d96de82fa7d5f4074c88863c1732363530c12d39
Diff: https://reviews.apache.org/r/54723/diff/
Testing
---
gradle rat check passes
Geode book builds with no broken links
Thanks,
Karen Miller
second commit before merging to develop.
- Karen
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54723/#review159073
-------
On Dec. 14, 2016, 4:33 p.m., Karen Miller wrote:
>
>
/diff/
Testing
---
gradle rat check passes
Thanks,
Karen Miller
/
Testing
---
gradle rat check passes
Thanks,
Karen Miller
Can someone with the proper karma help or show me how to integrate
commits to the new geode-examples repository with Geode JIRA
tickets and this mailing list? Thanks.
Yes. I'm moving everything over now, and after moving will remove it from
the
geode repository. See https://issues.apache.org/jira/browse/GEODE-2260.
On Tue, Jan 3, 2017 at 2:02 PM, Kirk Lund wrote:
> What's the plan for the new geode-examples repo and the existing
> geode-examples module of t
he patch at:
>
> https://github.com/apache/geode-examples/pull/1.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #1
>
>
> commit 6b7eacb2bfb196b1aa39069544
involving Examples.
Thanks,
Karen Miller
It's been a full week, but I haven't gotten any reviews on GEODE-2260, to
remove the geode-examples module from the geode repository. I'm not
a build/gradle expert, and this commit changes the build, so it really needs
some reviews.
The review request is https://reviews.apache.org/r/55393/
Thank
I'm going to pull this in and then update Geode web page.
On Wed, Jan 11, 2017 at 4:50 PM, joeymcallister wrote:
> Github user joeymcallister commented on a diff in the pull request:
>
> https://github.com/apache/geode/pull/334#discussion_r95706396
>
> --- Diff: geode-book/README.md ---
61 matches
Mail list logo
