Stream: jsCoq

Topic: Branch naming and Coq's CI

Emilio Jesús Gallego Arias (Nov 02 2022 at 18:09):

Hi folks, I've been thinking for a while on submitting jsCoq to Coq's CI.

In the past, I didn't do so because it was easier for everyone (and more CI use friendly) to have jsCoq repaired by me on each release; however, recent changes on the development model of Coq mean we should be in the CI.

So for that, we need to keep a "master" branch of jsCoq in our repos, so a proposal would be:

• have the main branch track Coq's main
• we branch for 8.17 etc when Coq branches (more or less)

What do you think @Ramkumar Ramachandra @Shachar Itzhaky

Shachar Itzhaky (Nov 02 2022 at 18:12):

I agree, this matches the standard way of works in most projects. I kind of like having the version right there on the master branch but setting the default each time is a bore since tooling is not designed to support this mode of work.

Last updated: Jun 04 2023 at 23:30 UTC