Set up process for auditing all Spark commits to assess impact on Comet

[andygrove]

What is the problem the feature request solves?

I would like a process that we follow, perhaps on a weekly basis, to look at new commits on each relevant Spark branch to asses any impact on Comet.

This is a task well suited to LLMs.

Describe the potential solution

No response

Additional context

No response

[coderfender]

Agreed ! But keeping track of all vs say tracking each release / branch might be a good first step ?

[andygrove]

Agreed ! But keeping track of all vs say tracking each release / branch might be a good first step ?

I suggest we start doing this for all commits to spark master/main branch since the 4.2 branch was cut. This way we will catch issues before the 4.3 branch is created and give us time to respond.

[coderfender]

Sure !