I just transferred the go related, open issues to arrow-go. We will leave closed/merged issues in the main repo to not break the association between commit message 'GH-...' and issue number as the transfer will renumber the issues.
Am Do., 29. Aug. 2024 um 08:56 Uhr schrieb Sutou Kouhei <k...@clear-code.com >: > Hi, > > I've created apache/arrow-go and opened issues on > apache/arrow-go and apache/arrow: > > * https://github.com/apache/arrow-go/issues > * > https://github.com/apache/arrow/issues?q=is%3Aissue+is%3Aopen+label%3A%22Component%3A+Go%22 > (#43872 or later) > > > https://github.com/apache/arrow-go/issues/1 (Import commits > from apache/arrow) is the first task. Could someone review > the command lines in the issue? If it looks good, I'll do > it. Then we can work on other issues together. > > > Thanks, > -- > kou > > In <20240829.115542.1508606970083169322....@clear-code.com> > "[RESULT][VOTE] Split Go release process" on Thu, 29 Aug 2024 11:55:42 > +0900 (JST), > Sutou Kouhei <k...@clear-code.com> wrote: > > > Hi, > > > > The vote carries with: > > > > 7 +1 (binding): > > Sutou Kouhei, David Li, Matt Topol, Raúl Cumplido, > > Antoine Pitrou, Joris Van den Bossche, Uwe L. Korn > > 4 +1 (non-binding): > > Jacob Wujciak, Ruoxi Sun, Xuwei Fu, Joel Lubinitsk > > 0 0: > > 0 -1: > > > > I'll list tasks for this and share them here as the first > > step. Please help us by writing, reviewing, testing and so > > on if you're interested in this. > > > > Thanks, > > -- > > kou > > > > In <20240826.113702.1496714896073155680....@clear-code.com> > > "[VOTE] Split Go release process" on Mon, 26 Aug 2024 11:37:02 +0900 > (JST), > > Sutou Kouhei <k...@clear-code.com> wrote: > > > >> Hi, > >> > >> I would like to propose splitting Go release process. > >> > >> Motivation: > >> > >> * We want to reduce needless major releases because major > >> releases require users' change > >> > >> Approach: > >> > >> 1. Extract go/ in apache/arrow to apache/arrow-go like > >> apache/arrow-rs > >> * Filter go/ related commits from apache/arrow and create > >> apache/arrow-go with them like we did for apache/arrow-rs > >> * Remove go/ related codes from apache/arrow > >> 2. Prepare integration test CI like apache/arrow-rs does: > >> > https://github.com/apache/arrow-rs/blob/master/.github/workflows/integration.yml > >> 3. Prepare release script based on apache/arrow-julia, > >> apache/arrow-adbc and/or apache/arrow-flight-sql-postgresql > >> > >> New release process: > >> > >> * apache/arrow-go will be released separated from > >> apache/arrow > >> * Matt or Joel will be a release manager of apache/arrow-go > >> * apache/arrow releases a new major version per 3-4 months > >> but apache/arrow-go will use more longer major release > >> cycle > >> * apache/arrow-go will use more minor/patch releases than > >> apache/arrow > >> > >> Impact on users: > >> > >> * Users need to update their import paths to > >> github.com/apache/arrow-go/v${VERSION}/arrow > <http://github.com/apache/arrow-go/v$%7BVERSION%7D/arrow> from > >> github.com/apache/arrow/go/v${VERSION}/arrow > <http://github.com/apache/arrow/go/v$%7BVERSION%7D/arrow> > >> * Currently, users need to update their import paths per > >> 3-4 months because apache/arrow uses a new major version > >> per 3-4 months. So this will not a big impact for the > >> current users. > >> > >> > >> See also the discussion of this: > >> https://lists.apache.org/thread/fstyfvzczntt9mpnd4f0b39lzb8cxlyf > >> > >> > >> The vote will be open for at least 72 hours. > >> > >> [ ] +1 Accept this proposal > >> [ ] +0 > >> [ ] -1 Do not accept this proposal because... > >> > >> > >> Thanks, > >> -- > >> kou >
