> What is the suggested flow for the forked repositories? GitHub has stated that they will be implementing changes this year to make this process smoother which is why I suggested waiting on this in the JIRA. At minimum this has been stated to include retargeting open pull requests. New pull requests would also go to the new default branch. So I don't forsee any necessary changes to forked repositories.
> Does that mean we must stop using Jenkins immediately? I don't believe so. The term slave has already been replaced by Jenkins. There is ongoing work in the Jenkins community to replace the term master with "controller." We can let them follow their own process. > "main" does sound like a significantly broader term, and it might require > extra clarification when used. Given that GitHub has already announced their intention to change the default branch name to main, I suspect that if this is a problem, it would not be specific to Calcite and will also resolve itself as the use of "main" becomes more common. -- Michael Mior [email protected] Le ven. 7 août 2020 à 03:59, Vladimir Sitnikov <[email protected]> a écrit : > > What is the suggested flow for the forked repositories? > The forks would probably need to make adjustments: either rename the branch > or re-target the branch (and update CI configuration). > > I don't think a volunteer can help with updating forks including private > ones :( > > Even if we rename `master` branch, Calcite would still use the labor of > Jenkins slaves that are controlled by Jenkins master to verify Calcite > quality. > Does that mean we must stop using Jenkins immediately? > > AFAIK there's just one week left before https://builds.apache.org/ > decommission (~15 > Aug or so), so we need to migrate to https://ci-builds.apache.org/ or > reject Jenkins to avoid slavery. > > -- > > Just in case: as a non-native speaker, I treat "master branch" and "main > branch" virtually indistinguishable. > However, "master branch" has a strong reference to the name of a Git > branch, while "main branch" sounds more like "a branch which is used a main > for some reason". > In other words, "main" does sound like a significantly broader term, and it > might require extra clarification when used. > > Vladimir
