Our contributing guidelines [1] state that a fork must be used, so I'd say
that should be the way to proceed (unless there's an exceptional
circumstance).
Best,
Ruben
[1] https://calcite.apache.org/develop/#contributing
On Tue, Apr 29, 2025 at 11:32 AM Alessandro Solimando <
alessandro.solima..
Hi Stamatis,
thank you for bringing this up.
Personally, I am used to the fork-based approach and I have never
experienced the need to create a branch under the apache/calcite repo that
I couldn't achieve via a branch in the fork + a (sometimes draft) PR.
Not against either if there is a rational
Hey everyone,
I noticed that some committers occasionally create dev branches under
the main apache/calcite repository [1].
Working directly under the main apache/calcite repo has some side effects:
* Extra noise and duplicate notifications in commits list [2]
* Duplicate CI runs on Jenkins [3] a
