osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Making a bugfix 0.11.1 release


I'm having problems with Crossbow. I am going to try a few things
(going through the setup process "from scratch" -- new tokens, new
local repositories, etc.) but if I can't figure it out today, a
different PMC with a working Crossbow setup may need to cut the
release candidate artifacts
On Fri, Oct 19, 2018 at 10:48 AM Wes McKinney <wesmckinn@xxxxxxxxx> wrote:
>
> I prepared the maintenance branch here
>
> https://github.com/apache/arrow/tree/maint-0.11.x
>
> I'm not fully set up with to create a release candidate yet with
> Crossbow but I'll work on it today and try to get a vote started by
> EOD
> On Fri, Oct 19, 2018 at 3:45 AM Antoine Pitrou <antoine@xxxxxxxxxx> wrote:
> >
> >
> > I would recommend cherry-picking a minimal number of patches for the
> > bugfix and for packaging to work.  It's better not to include API
> > additions or changes.
> >
> > Regards
> >
> > Antoine.
> >
> >
> > Le 17/10/2018 à 03:32, Wes McKinney a écrit :
> > > hi folks,
> > >
> > > As a result of ARROW-3514, we need to release new Python packages
> > > quite urgently since major functionality (Parquet writing on many
> > > Linux platforms) is broken out of the box
> > >
> > > https://github.com/apache/arrow/commit/66d9a30a26e1659d9e992037339515e59a6ae518
> > >
> > > We have a couple options:
> > >
> > > * Release from master
> > > * Release 0.11.0 + minimum patches to include the ARROW-3514 fix and
> > > any follow up patches to fix packaging
> > >
> > > There is the option to "not" release but it could cause confusion for
> > > people because PyPI does not allow replacing wheels; a new version
> > > number has to be created.
> > >
> > > What would folks like to do? Who can help with the RM duties? Since a
> > > 72 hour vote is a _should_ rather than _must_, we could reasonably
> > > close the release vote in < 72 hours and push out packages faster if
> > > it is scope limited to the zlib bug fix
> > >
> > > Thanks,
> > > Wes
> > >