When I said “is there a significant problem” I meant an existing problem. I don’t think there is an existing problem. And if it ain’t broke, don’t fix it.
This change would be adding another thing for people voting on releases to review. I don’t want to add that burden. Julian > On Jul 2, 2019, at 11:32 AM, Vladimir Sitnikov <[email protected]> > wrote: > > Michael>We regularly force push to the Calcite repo, so this is not a > Michael>restriction we face. > > I suggest we just continue with that (fix small typos via amend/rebase) > > Michael>The two repos are already separate so I don't think this is a big > Michael>departure > > How are you going to check(test) cross-references between Avatica and > Calcite pages then? > > > Juiian>At a time when our release managers are more burdened than ever. > > My experience with pgjdbc shows that the more automated the release is the > simpler the role of a release manager is. > > Julian>Is there a significant problem where we publish a release and the > site is screwed up? > > That is not a problem at all for Gradle-based approach. > On top of that, Calcite/Avatica is not using GitHub pages yet, so there's > nothing to rollback. > > Vladimir
