Announcements are made for freezing/reopening here on the dev list - that's
about it I'm afraid. Generally speaking, branches are re-opened after
release automatically but the release manager still needs to bump to
SNAPSHOT on the branch. It's usually at that point the branch is officially
reopened
Do we have an overview anywhere of which branches are frozen at any given
time? I have been assuming branches were automatically opened once their
releases were done, but I see now that that is not necessarily the case😅
Searching through the mailing list to figure out which branches are frozen
can
There's a fair bit of work happening on 3.5-dev right now. It's probably
best to not slow down anyone's momentum on that to hold 3.5-dev frozen. If
we have to do a small 3.5.3 release alongside 3.6.0 to ensure functional
parity I guess that's fine. I think we can reopen 3.5-dev again. Please let
me
Hi folks, I've been away for a bit during the holiday but back now thinking
about this release. The issue for 3.4-dev that made me want to hold release
was resolved. The fix had nothing to do with the code itself and more to do
with the fact that memory requirements for the tests we'd added over th
I think we will need to take a bit of a delay on the code freeze for this
Friday. 3.4-dev is unstable in CI - i've been trying to get to the root of
the problem for a week now and it's still not completely resolved. That's
prevented me from looking at other issues I wanted to get done and I think
t
In the worst case, if there were things we wanted added to 3.6.0 that
weren't quite ready for code freeze we could release 3.5.2 and hold the
freeze on its branch while 3.6.0 finished. I just wouldn't want a 3.6.0 to
force a few commits into a fast turnaround release of 3.5.3. That might
give some
The work for adding a regex TextP is sitting on the TINKERPOP-2652 branch. I
still need to write the docs and add one last Java test but otherwise it's
close to PR ready. I would like to try and get that into 3.6 which I think I
should be able to do before the cutoff.
In general capturing what w
no - not yet fixed, but not forgotten. i'd consider that a blocker for
release. maybe i can do that today.
On Mon, Dec 13, 2021 at 8:45 AM Divij Vaidya
wrote:
> Hey Stephen
>
> Did we fix
> https://github.com/apache/tinkerpop/pull/1502#issuecomment-983549704 yet?
> I
> would suggest that we fix
Hey Stephen
Did we fix
https://github.com/apache/tinkerpop/pull/1502#issuecomment-983549704 yet? I
would suggest that we fix this known bug in a change we are about to
release for the sake of releasing a stable build.
Regards,
Divij Vaidya
On Mon, Dec 13, 2021 at 1:44 PM Stephen Mallette
wrot
I'd like to propose we do a release for the new year, with code freeze
starting conveniently on Friday December 31.
I think we should also consider making this the last release of 3.4.x.
It occurred to me that 3.6.x doesn't have a name yet. Working in reverse
(never done it this way before), I ha
10 matches
Mail list logo
