GitHub releases do have a prerelease/rc status that can be activated. Maybe
that could be used as an indicator to not include theses on the exchange
site?
Sarah Gilmore schrieb am Fr., 10. Nov.
2023, 21:06:
> Hi Raúl,
>
> > Currently all the binaries are generated on the third step of the
> >
Hi Raúl,
> Currently all the binaries are generated on the third step of the
> Release process [1] when we run `03-binary-submit.sh`. The crossbow
> job could build the MLTBX artifact and then when we do download the
> other binaries (`04-binary-download.sh`) we should also download the
> MTLBX
In case it was not clear, even though the binary job is run on
ursacomputing/crossbow when we upload the binaries and create the
Release that should be, at least in my opinion, an apache/arrow
release.
Both for the steps:
1. RC: Upload MLTBX to GitHub Releases for apache-arrow-X.Y.Z-rcN
and
2.2
Hi Sara,
El vie, 10 nov 2023 a las 18:48, Sarah Gilmore
() escribió:
>
> Hi Kou,
>
> > We can use apache/arrow's GitHub Releases. The release
> > distribution document says that we can use GitHub as a
> > release platform:
> > https://infra.apache.org/release-distribution.html#other-platforms
> >
Hi Kou,
> We can use apache/arrow's GitHub Releases. The release
> distribution document says that we can use GitHub as a
> release platform:
> https://infra.apache.org/release-distribution.html#other-platforms
>
> apache/arrow doesn't use GitHub Releases yet but
> apache/arrow-adbc and
