Hi all, to help us get ready, I've started a draft blog post for the 0.16
release: https://github.com/apache/arrow-site/pull/41
We'll need to fill in the sections. Feel free to push edits to my branch,
or you can also email me (personally is fine) and I can paste them in.
Neal
On Thu, Jan 9, 20
Understood and appreciated. Yeah, it can become a bit of a mess.
On Thu, Jan 9, 2020 at 12:22 PM Wes McKinney wrote:
> Will do -- there were many C++ and Python-related issues that I think
> were put in 1.0.0 / 0.16.0 overly optimistically and so I removed the
> Fix Version entirely (some of the
Will do -- there were many C++ and Python-related issues that I think
were put in 1.0.0 / 0.16.0 overly optimistically and so I removed the
Fix Version entirely (some of these had been pushed off 3-4 major
releases ago). I may have removed some Fix Versions from other
components that should have be
It would be helpful that when something is assigned to a release and you
want to push it out, you push it to the next release as opposed to removing
a fix version entirely. Thanks!
On Tue, Jan 7, 2020 at 10:26 AM Wes McKinney wrote:
> I just renamed the 1.0.0 release version in JIRA to 0.16.0 an
I just finished an initial curation of the JIRA backlog. There are now
137 issues which is probably more than will be resolved before
releasing. I noticed some concerning bugs that may need attention, but
if there are any new feature or nice-to-have issues that you are
familiar with please remove t
That sounds fine to me. I don't see many blocking issues for a major
release, and the nightly reports are fairly clean, so I think we
should try to be ready to go at the beginning of that week of the
19th.
On Tue, Jan 7, 2020 at 4:40 PM Neal Richardson
wrote:
>
> If we expect that the release pro
On Tue, Jan 7, 2020 at 11:40 PM Neal Richardson
wrote:
>
> If we expect that the release process may be less stable this time, should
> we bump up our target date for an RC, like to the 20th or 21st (two weeks
> from now)? That would give us more leeway to make sure we get a release out
> before t
If we expect that the release process may be less stable this time, should
we bump up our target date for an RC, like to the 20th or 21st (two weeks
from now)? That would give us more leeway to make sure we get a release out
before the end of January.
Neal
On Tue, Jan 7, 2020 at 1:02 PM Krisztián
Sounds good to me. I'll help with the jira curation.
Because of the recent CI migrations we'll need to be more thorough during
the verification, and I also expect minor issues during the release process.
So I volunteer to be the RM if no one else wants to jump in.
Thanks, Krisztian
On Tue, Jan 7
Thanks, Wes. I made
https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.16.0+Release to
help us track 0.16.
Neal
On Tue, Jan 7, 2020 at 10:26 AM Wes McKinney wrote:
> I just renamed the 1.0.0 release version in JIRA to 0.16.0 and will
> work on removing issues that are not necessary to be
I just renamed the 1.0.0 release version in JIRA to 0.16.0 and will
work on removing issues that are not necessary to be able to release
(others, please help). If we make miraculous progress with the 1.0.0
columnar format blockers (per discussion below), we can change this
back, but I think either
11 matches
Mail list logo
