/jira/browse/TINKERPOP-1980
>>>
>>> Should be good to go now.
>>>
>>> -----Ursprüngliche Nachricht-
>>> Von: Stephen Mallette
>>> Gesendet: Montag, 7. Januar 2019 13:44
>>> An: dev@tinkerpop.apache.org
>>> Betref
Should be good to go now.
>>
>> -Ursprüngliche Nachricht-
>> Von: Stephen Mallette
>> Gesendet: Montag, 7. Januar 2019 13:44
>> An: dev@tinkerpop.apache.org
>> Betreff: Re: [DISCUSS] code freeze 3.2.11/3.3.5/3.4.0
>>
>> You can CTR the c
icht-
> Von: Stephen Mallette
> Gesendet: Montag, 7. Januar 2019 13:44
> An: dev@tinkerpop.apache.org
> Betreff: Re: [DISCUSS] code freeze 3.2.11/3.3.5/3.4.0
>
> You can CTR the commit to master now so that it's there for when I go
> through the binary release process tomorrow
now.
-Ursprüngliche Nachricht-
Von: Stephen Mallette
Gesendet: Montag, 7. Januar 2019 13:44
An: dev@tinkerpop.apache.org
Betreff: Re: [DISCUSS] code freeze 3.2.11/3.3.5/3.4.0
You can CTR the commit to master now so that it's there for when I go through
the binary release process
uar 2019 13:07
> An: dev@tinkerpop.apache.org
> Betreff: Re: [DISCUSS] code freeze 3.2.11/3.3.5/3.4.0
>
> Florian - i suppose this one needs to be done?
>
> https://issues.apache.org/jira/browse/TINKERPOP-1980
>
> should it have been done before we tagged 3.4.0 and buil
An: dev@tinkerpop.apache.org
Betreff: Re: [DISCUSS] code freeze 3.2.11/3.3.5/3.4.0
Florian - i suppose this one needs to be done?
https://issues.apache.org/jira/browse/TINKERPOP-1980
should it have been done before we tagged 3.4.0 and built all the artifacts?
does it matter?
On Fri, Jan 4, 2019
Florian - i suppose this one needs to be done?
https://issues.apache.org/jira/browse/TINKERPOP-1980
should it have been done before we tagged 3.4.0 and built all the
artifacts? does it matter?
On Fri, Jan 4, 2019 at 4:52 PM Stephen Mallette
wrote:
> well - that was absolute insanity right
well - that was absolute insanity right down the valid-distiribution.sh on
3.4.0. Please make sure you pull master before testing 3.4.0 as kuppitz had
to drop in a patch..
On Wed, Jan 2, 2019 at 4:50 PM Stephen Mallette
wrote:
> so, 3.2.11 and 3.3.5 releases are prepared - vote threads
so, 3.2.11 and 3.3.5 releases are prepared - vote threads were just sent. i
would have had 3.4.0 done too but i flubbed the 2018/2019 date on 3.3.5 and
had to redo the whole thing basically - so that was rotten. I'll have 3.4.0
out tomorrow.
On Wed, Jan 2, 2019 at 7:34 AM Stephen Mallette
wrote:
yes. i can also use a specific commit, but it invariably leaves out commits
for a release. i guess those commits left out will just be release manager
commits typically, but i dunno, it just bugged me that it wasn't the actual
3.2.10..3.2.11
On Wed, Jan 2, 2019 at 7:15 AM Robert Dale wrote:
>
Can't you just use HEAD?
git shortlog -sn 3.2.10..HEAD
Robert Dale
On Wed, Jan 2, 2019 at 7:11 AM Stephen Mallette
wrote:
> All PRs appear mergedI've starting the release process beginning with
> 3.2.11. Should see VOTE threads coming soon.
>
> Separately, I already found a problem with
All PRs appear mergedI've starting the release process beginning with
3.2.11. Should see VOTE threads coming soon.
Separately, I already found a problem with using git shortlog to generate
the "contributor list" as there is no 3.2.11 tag to use in the arguments
given to it. It's a bit of a
I don't know what is going on but yesterday i spent a few minutes messing
with the failing python build with radish and after a few failures it just
started working again locally. Then I re-ran failed travis jobs and they
started passing. I guess the problem was fixed externally - weird. I
expect
A quick & dirty fix for the broken radish libs to at least get a clean
build in docker:
diff --git a/docker/scripts/build.sh b/docker/scripts/build.sh
index e172ddaaa9..8b56cf53c3 100755
--- a/docker/scripts/build.sh
+++ b/docker/scripts/build.sh
*@@ -78,7 +78,10 @@* if [ -r "settings.xml" ];
Hi all, just checking in during the holiday period. My laptop will return
to the off position shortly, but I wanted to point out that we seem to have
a problem with Python:
https://travis-ci.org/apache/tinkerpop/jobs/472444735
every current PR seems to be in fail mode right now. We will want to
While I think we could go on for every adding things to 3.4.0 I think it's
time to cut it off and release. There's too many good things in there to
hold for any longer. We are looking at releasing 3.2.11, 3.3.5 and 3.4.0.
I'd propose we polish up remaining items this week, set for code freeze
16 matches
Mail list logo
