Hi, Actually I double checked it and the default branch on jenkins is `master`. So `benchmark-request` branch can be safely removed without any further changes.
Best, Piotrek pon., 31 paź 2022 o 10:34 Leonard Xu <xbjt...@gmail.com> napisał(a): > > So the > > benchmark_request could be deleted, but only if someone would also clean > > up/adjust the Jenkins's job default parameters. > > Thanks @Piotr for suppling this background. > As an upstream repository, I tend to keep it as clean as possible. > These users(I think they’re experienced developers) with benchmark > requirements can also checkout/adjust branch from their own repository. > Thus I tend to delete this branch now，HDYT? > > Best, > Leonard > > > > > Best, > > Piotrek > > > > pon., 31 paź 2022 o 03:23 Jark Wu <imj...@gmail.com> napisał(a): > > > >> Thank you for driving this effort, Leonard! > >> > >> Best, > >> Jark > >> > >>> 2022年10月28日 11:25，Yuan Mei <yuanmei.w...@gmail.com> 写道： > >>> > >>> Hey Leonard, > >>> > >>> Thanks for your efforts to clean up our repo! > >>> > >>> Best > >>> Yuan > >>> > >>> > >>> > >>> On Thu, Oct 27, 2022 at 11:55 PM Leonard Xu <xbjt...@gmail.com> wrote: > >>> > >>>> Thanks Matthias and Chesnay for the quick ACK. > >>>> > >>>> I’ve deleted following branches. > >>>>> FLINK-29638-1.15 > >>>>> FLINK-29638-1.16 > >>>>> 28733 > >>>>> revert-16606-materialization_on_runtime > >>>>> release0 Updated 2 years > ago > >>>>> docs_experimental__docs Updated 2 years ago > >>>>> docs_experimental__docs_compile Updated 3 years ago > >>>> > >>>> BTW, I fork a Flink repo [1] as a backup to avoid we delete required > >>>> branches. > >>>> > >>>> > >>>> Best, > >>>> Leonard > >>>> [1] https://github.com/flink-tpc-ds/flink-221027 > >> > >> > >
