; See also:
> > > >
> > >
> > https://lists.apache.org/list.html?dev@arrow.apache.org:lte=1M:%5BNIGHTLY%5D
> > > >
> > > > There are some failures everyday.
> > > > If we have any failures, we can't produce release artifacts.
> &g
IGHTLY]" report everyday from dev@.
> > > See also:
> > >
> >
> https://lists.apache.org/list.html?dev@arrow.apache.org:lte=1M:%5BNIGHTLY%5D
> > >
> > > There are some failures everyday.
> > > If we have any failures, we can't produce
elease a
> > new version. If we keep all nightly builds green, we will be
> > able to release a new version soon when we want to release.
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In
> > "Re: [Discuss] Arrow Release Schedul
n. If we keep all nightly builds green, we will be
> able to release a new version soon when we want to release.
>
>
> Thanks,
> --
> kou
>
> In
> "Re: [Discuss] Arrow Release Schedule" on Tue, 10 Nov 2020 18:23:16
> -0600,
> Wes McKinney wrote:
&
artifacts.
In recent releases, we fix these failures when we release a
new version. If we keep all nightly builds green, we will be
able to release a new version soon when we want to release.
Thanks,
--
kou
In
"Re: [Discuss] Arrow Release Schedule" on Tue, 10 Nov 2020 18:23:16 -0600
We do need a PMC member to sign the release artifacts. Aside from
that, IMHO there is a lot that can be done to improve the automation
around producing the release artifacts and preparing the release
branch.
As Krisztian can attest, producing a release currently requires a
_lot_ of human time (and
Hi Wes,
Is it only the PMC members that can volunteer to drive this or can someone
from the community volunteer and drive as well if they desire to have a
release sooner?
I see that the release process has a fairly comprehensive checklist of
tasks here(
https://cwiki.apache.org/confluence/display
I think to release more often, a few things are necessary:
- Other organizations / PMC members must volunteer more time to drive
releases and the process around them. My team (and Krisztian in particular)
together with Kou and Uwe have done the majority of this work the last
couple of years.
- So
>
> Are there any plans for a more frequent release cadence?
Not to my knowledge. The release process is still relatively heavy weight.
Do we have a guide for what goes into major releases vs. minor releases
> vs. patch releases?
In the current regime [1] we don't expect minor release. So maj
Hello,
My understanding is that Arrow releases are 3 months apart. Are there any
plans for a more frequent release cadence? Do we have a guide for what goes
into major releases vs. minor releases vs. patch releases?
Thanks,
--
*James Duong*
Lead Software Developer
Bit Quill Technologies Inc.
D
10 matches
Mail list logo
