Yes, it's my first task this morning
On Nov 13, 2018 07:02, "Anthony Baker" wrote:
Are you able to send out a draft for review today?
> On Nov 7, 2018, at 12:43 PM, Robert Houghton wrote:
>
> I volunteer as tribute
>
> On Nov 7, 2018 12:42, "Anthony Baker" wrote:
>
> We need to prepare a
Hey Jens,
No worries at all, it's fixed now.
Cheers.
On Tue, Nov 13, 2018 at 3:33 PM Jens Deppe wrote:
> No worries, and thanks for the heads-up Juan.
>
> I'm really not sure anything can be done that wouldn't end up being
> heavy-handed and mostly just be an impedance.
>
> I should have sent
@Patrick Rhomberg I've never seen the
dependencyManagement element survive in a published POM before.
Since it sounds like you're asserting that you saw that element in a
published POM (published by Gradle), I decided to verify that. I ran this
from the Geode develop branch just now:
./gradlew
No worries, and thanks for the heads-up Juan.
I'm really not sure anything can be done that wouldn't end up being
heavy-handed and mostly just be an impedance.
I should have sent out a notice describing the commons-lang change (given
its scope) and that any in-flight PRs might be affected.
Are you able to send out a draft for review today?
> On Nov 7, 2018, at 12:43 PM, Robert Houghton wrote:
>
> I volunteer as tribute
>
> On Nov 7, 2018 12:42, "Anthony Baker" wrote:
>
> We need to prepare a report for the ASF Board by Nov 14. Any volunteers to
> write up a draft?
>
> You
Hello devs,
Compilation in *develop* is failing after my latest commit.
Long story short: the *concourse-ci* tests were all green but the
*commons-lang* version was upgraded in develop *AFTER* the build finished
but *BEFORE* the merge was executed, so the import is currently outdated
(should be
Thank you, Owen!
On Mon, Nov 12, 2018 at 9:08 PM Owen Nichols wrote:
> Pipeline is up:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-8-0-main
> <
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-8-0-main
> >
>
> > On Nov 12, 2018, at
@Everyone
After some investigation with Kirk, it appears that the newer Concourse PR
resource prioritizes commit time as part of its identification of "newer"
commits on a given PR's branch.
As a result, you can accidentally paint yourself into a corner with git
rebase if your (actually newer)
Patrick helped me figure this out! Whew, whatta relief. I'll let him
describe it so others benefit (it has something to do with commit time
instead of push time or changes to head sha)...
Thanks,
Kirk
On Tue, Nov 13, 2018 at 9:31 AM, Kirk Lund wrote:
> Just in case you don't believe me and
+1 I like this idea, but I recognize that it will be a challenge when there
is still some flakiness to the pipeline. I think we'd need clear
guidelines on what to do if your PR fails due to something seemingly
unrelated. For instance, we ran into GEODE-5943 (flaky EvictionDUnitTest)
in our last
+1 I've had to reorder the list a few times myself to correct the ordering
On Mon, Nov 12, 2018 at 5:28 PM, Galen O'Sullivan
wrote:
> Hi all,
>
> I wrote a PR (GEODE-5800) recently to remove redundant cases from
> DataSerializer.readObject etc. calls. This changed the bytecode size (but
> not
Thanks Robert, comments below.
> On Nov 13, 2018, at 12:33 PM, Robert Houghton wrote:
>
> Here is a draft of the GEODE report. Please comment or amend so that we can
> submit to Apache.
> Thank you,
> -Robert Houghton
>
> ## Description:
> Apache Geode provides a database-like consistency
Here is a draft of the GEODE report. Please comment or amend so that we can
submit to Apache.
Thank you,
-Robert Houghton
## Description:
Apache Geode provides a database-like consistency model, reliable
transaction
processing and a shared-nothing architecture to maintain very low latency
If you'd like Maven dependencyManagement like behavior in Gradle, then you
should have a look at...
https://github.com/spring-gradle-plugins/dependency-management-plugin
-j
On Tue, Nov 13, 2018 at 8:10 AM, Bill Burcham wrote:
> @Patrick Rhomberg I've never seen the
> dependencyManagement
Just in case you don't believe me and want to double-check my answer:
My PR which says there are NO CONFLICTS:
https://github.com/apache/geode/pull/2778
Thanks,
Kirk
On Tue, Nov 13, 2018 at 9:31 AM, Kirk Lund wrote:
> Yes github says it merges cleanly (still does in fact):
>
> This branch has
Yes github says it merges cleanly (still does in fact):
This branch has no conflicts with the base branch when rebasingRebase and
merge can be performed automatically.
The previous revision DID have a merge conflict which is exactly why I
rebased on develop, resolved conflicts and then pushed to
If it makes easy to find/address failure with AnalyzeSerializablesTest, +1
-Anil.
On Tue, Nov 13, 2018 at 9:34 AM Kirk Lund wrote:
> +1 I've had to reorder the list a few times myself to correct the ordering
>
> On Mon, Nov 12, 2018 at 5:28 PM, Galen O'Sullivan
> wrote:
>
> > Hi all,
> >
> >
I categorically like style improvement and enforcement.
+1 to this specific style improvement and enforcement.
It's pretty straight-forward to write a regex into our spotless.gradle.
Let me know if you need a hand on that front, since I know I shouldn't use
"straightforward" to refer to either
18 matches
Mail list logo
