Hi, > Kou, would you be interested in taking the task of submitting to Debian and > Fedora the arrow library?
I'm sorry but I'm not interested in it. I have only limited time because I'm not a full-time Apache Arrow developer. I want to spent my time for Ruby related work as much as possible. (I'm busy until the end of April for work and RubyKaigi 2019.) > Is there anything we can do to help? I listed items what we need to work. Thanks, -- kou In <CAOrRV3ds04-rrWzbexyZmmbmTqbD=_EqVOuPeUdR_Mu=89u...@mail.gmail.com> "Re: Distributing Arrow in Debian and Fedora" on Wed, 6 Feb 2019 12:50:24 -0800, Javier Luraschi <jav...@rstudio.com> wrote: > Kou, would you be interested in taking the task of submitting to Debian and > Fedora the arrow library? It would be ideal since it seems like you have a > clear understanding of what needs to be done. Is there a timeline you would > want to follow? Is there anything we can do to help? > > On Wed, Feb 6, 2019 at 12:34 AM Jeroen Ooms <jeroeno...@gmail.com> wrote: > >> On Sat, Feb 2, 2019 at 10:29 PM Kouhei Sutou <k...@clear-code.com> wrote: >> > We need to consider how to update package versions. >> > We'll release Apache Arrow more frequency than Debian and >> > Fedora. If we don't update packages on Debian and Fedora, >> > they will ship old Apache Arrow. >> >> I think it's initially fine to upload frequently because there are no >> reverse dependencies yet. But once other Debian packages start >> depending in libarrow, you need to coordinate releases with those >> other packages if the api has breaking changes. >> >> > We may be able to use stable-updates for providing the >> > latest Apache Arrow to Debian users: >> > https://wiki.debian.org/StableUpdates >> >> For the purpose of CRAN, having arrow in the 'testing' branch of >> Debian is sufficient. Packages that are uploaded into unstable (sid) >> automatically get promoted to 'testing' after 2 weeks if they pass all >> checks. We don't have to wait for a stable Debian release. >>
