FYI, I also created the skeleton for the release blog post at
https://github.com/apache/arrow-site/pull/153/files
This should give everyone time to fill the proper parts of the blog post
using github commit suggestions

Ignore the blog post date, I just put any random future date, which will
have to be updated when we actually publish the release.

On Thu, Oct 14, 2021 at 10:24 AM Alessandro Molina <
alessan...@ursacomputing.com> wrote:

> Seems the tentative release date will probably slip to Monday/Tuesday next
> week. There has been some delay generated by the release of Python3.10 in
> the hope we could already include support for it in the current release.
>
> There are a total of 30+ started issues as the moment, it would be great
> if the owners could defer to v7.0.0 those that they don't think can close
> in time for Monday
>
> On Mon, Oct 4, 2021 at 1:38 PM Krisztián Szűcs <szucs.kriszt...@gmail.com>
> wrote:
>
>> Aiming the first release candidate for Oct 14th/15th sounds good to me.
>>
>> On Mon, Oct 4, 2021 at 10:35 AM Alessandro Molina
>> <alessan...@ursacomputing.com> wrote:
>> >
>> > If possible I think it makes sense to aim for the week of 11th,
>> > if there is any blocker or major issues that gets raised and for which
>> we
>> > need to wait we can defer to the week of 18th.
>> >
>> > As far as it's 2nd/3rd week of the month I don't think it makes any
>> major
>> > difference.
>> > Obviously when Krisztian will be able to cut the release plays the
>> biggest
>> > role here, so I'm willing to hear his opinion about what we can aim for.
>> >
>> > On Mon, Oct 4, 2021 at 3:48 AM Micah Kornfield <emkornfi...@gmail.com>
>> > wrote:
>> >
>> > > Hi
>> > > I Just wanted to clarify we are aiming at cutting the first release
>> > > candidate for the main report the week of the 11th or 18th?
>> > >
>> > > Thanks,
>> > > Micah
>> > >
>> > > On Sat, Oct 2, 2021 at 3:27 AM Andrew Lamb <al...@influxdata.com>
>> wrote:
>> > >
>> > > > FYI as we did with the arrow-rs 5.0 release, I will prepare an
>> arrow-rs
>> > > > 6.0.0 release approximately concurrently with the other languages.
>> > > >
>> > > > I will tentatively aiim to create an arrow-rs 6.0 candidate on
>> October 14
>> > > > or October 15 (assuming it is approved, it would be released on or
>> around
>> > > > October 18, 2021).
>> > > >
>> > > > Please let me know if there are any concerns with this schedule
>> > > > Andrew
>> > > >
>> > > > On Fri, Oct 1, 2021 at 3:34 AM Alessandro Molina <
>> > > > alessan...@ursacomputing.com> wrote:
>> > > >
>> > > > > In preparation for release 6.0.0 which should probably happen
>> within
>> > > the
>> > > > > next 2-3 weeks according to the usual release cycle the
>> Confluence page
>> > > > for
>> > > > > the release has been created (
>> > > > >
>> https://cwiki.apache.org/confluence/display/ARROW/Arrow+6.0.0+Release
>> > > )
>> > > > >
>> > > > > Also all non Bug issues that were not started have been moved to
>> > > version
>> > > > > 7.0.0, please do not create new issues under 6.0.0 unless you
>> expect to
>> > > > be
>> > > > > able to solve them within the next few days. Likewise, feel free
>> to
>> > > move
>> > > > > back to version 6.0.0 things that you expect to be able to address
>> > > within
>> > > > > the next few days.
>> > > > >
>> > > > > That leaves the release with a total of ~60 bugs pending. It's
>> probably
>> > > > > unrealistic that those can be fixed in 2-3 weeks, so I encourage
>> the
>> > > > owners
>> > > > > of those issues to go through them and postpone them to version
>> 7.0.0
>> > > > > unless they plan to address them soon. The remaining ones will be
>> moved
>> > > > to
>> > > > > version 7.0.0 before the release.
>> > > > >
>> > > > > Thanks everybody for the big effort in contributing to a release
>> that
>> > > > > includes nearly 500 issues and if you are aware of any blocker
>> (apart
>> > > > those
>> > > > > already marked as blockers in the Confluence page) please raise
>> them
>> > > > early
>> > > > > on so that there is enough time to address them.
>> > > > >
>> > > >
>> > >
>>
>

Reply via email to