his automatically by creating a cloned
> > > Git repository for test.
> > >
> > > It's better that we have a Web site to show generated pages.
> > > We can create
> > > https://github.com/apache/arrow-site/tree/asf-site/nightly
> > > and use it
site for this? (arrow-nightly.ursalabs.org?)
> >
> > dev/release/post-04-rubygems.sh:
> >
> > We may be able to use GitHub Package Registry[2] to upload
> > RubyGems. We can use "pre-release" package feature of
> > https://rubygems.org/ but it's not s
e to use GitHub Package Registry[2] to upload
> RubyGems. We can use "pre-release" package feature of
> https://rubygems.org/ but it's not suitable for
> nightly. It's for RC or beta release.
>
> [2] https://github.blog/2019-05-10-introducing-github-package-registry/
>
.sh:
We may be able to use GitHub Package Registry[2] to upload
NuGet packages.
dev/release/post-07-rust.sh:
I don't have any idea. But it must be ran
automatically. It's always failed. I needed to run each
command manually.
dev/release/post-08-remove-rc.sh:
We'll be able to skip th
tashes. I
> > > >> > > > don't have time to create pull requests for them
> > > >> > > > yet. Because I postponed some tasks of my main
> > > >> > > > business. I'll create pull requests after I finished the
> > > >&g
ed the
> > >> > > > postponed tasks of my main business.)
> > >> > > >
> > >> > >
> > >> > > Thanks. I'll follow up on the 0.14.1/0.15.0 thread -- since we
> need to
> > >> > > release agai
;
> >> > >
> >> > > Thanks. I'll follow up on the 0.14.1/0.15.0 thread -- since we need to
> >> > > release again soon because of problems with 0.14.0 please let us know
> >> > > what patches will be needed to make another release.
oblems related to dev/release/ in our normal
>> > > > development process, release process will be less painful.
>> > > >
>> > > > The biggest problem for 0.14.0 RC0 is java/pom.xml related:
>> > > > https://github.com/apache/arrow/pull/4717
>>
gt; > > > It was difficult for me because I don't have Java
> > > > knowledge. Release manager needs help from many developers
> > > > because release manager may not have knowledge of all
> > > > supported languages. Apache Arrow supports 10 over
> > > &g
ge. Release manager needs help from many developers
> > > because release manager may not have knowledge of all
> > > supported languages. Apache Arrow supports 10 over
> > > languages.
> > >
> > >
> > > For Bintray API limit problem, we'll be able t
he Arrow supports 10 over
> > languages.
> >
> >
> > For Bintray API limit problem, we'll be able to resolve it.
> > I was added to https://bintray.com/apache/ members:
> >
> > https://issues.apache.org/jira/browse/INFRA-18698
> >
> > I'l
bintray.com/apache/ members:
>
> https://issues.apache.org/jira/browse/INFRA-18698
>
> I'll be able to use Bintray API without limitation in the
> future. Release managers should also request the same thing.
>
This is good, I will add myself. Other PMC members should also add
e. Release managers should also request the same thing.
Thanks,
--
kou
In
"[DISCUSS] Release cadence and release vote conventions" on Sat, 6 Jul 2019
16:28:50 -0500,
Wes McKinney wrote:
> hi folks,
>
> As a reminder, particularly since we have many new community member
hi folks,
As a reminder, particularly since we have many new community members
(some of whom have never been involved with an ASF project before),
releases are approved exclusively by the PMC and in general releases
cannot be vetoed. In spite of that, we strive to make releases that
have unanimous
14 matches
Mail list logo
