Ok - I think the issue is resolved now. 3.5-dev is now open for business.
For now we still have 3.5-dev-busted (which is the state 3.5-dev was in
when we realized it was bad) and 3.5-dev-august-23 which was Florian's
local working state that did not seem to look corrupted somehow. I imagine
that
[
https://issues.apache.org/jira/browse/TINKERPOP-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408181#comment-17408181
]
Stephen Mallette commented on TINKERPOP-2504:
-
The 3.5-dev branch had to be rebuilt after
[
https://issues.apache.org/jira/browse/TINKERPOP-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408179#comment-17408179
]
Stephen Mallette commented on TINKERPOP-2592:
-
The 3.5-dev branch had to be rebuilt after
[
https://issues.apache.org/jira/browse/TINKERPOP-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408180#comment-17408180
]
Stephen Mallette commented on TINKERPOP-2593:
-
The 3.5-dev branch had to be rebuilt after
[
https://issues.apache.org/jira/browse/TINKERPOP-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408178#comment-17408178
]
Stephen Mallette commented on TINKERPOP-2591:
-
The 3.5-dev branch had to be rebuilt after
[
https://issues.apache.org/jira/browse/TINKERPOP-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408177#comment-17408177
]
Stephen Mallette commented on TINKERPOP-2582:
-
The 3.5-dev branch had to be rebuilt after
[
https://issues.apache.org/jira/browse/TINKERPOP-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408175#comment-17408175
]
Stephen Mallette commented on TINKERPOP-2585:
-
The 3.5-dev branch had to be rebuilt after
Your branch looks a little strange. While it definitely seems to have no
mix up with master, it also seems to lack things I expected to
see...anyway, let's leave your branch there for a bit for safety sake.
Glad you had that. Resetting the branch now.
On Wed, Sep 1, 2021 at 3:02 AM
> One caveat to that - Florian, I had a bit of trouble sorting through your
> dependabot merges. I assume dependabot will just create fresh PRs for you to
> merge when we force push this to 3.5-dev?
you could just merge them in again?
Yes, that shouldn't be a problem.
It looks like you already