Re: [VOTE] move Apahe OpenJPA from SVN to gitbox hosted at ASF

On 09/10/2018 17:24, Mark Struberg wrote: hi folks! Since the discuss thread showed good support I'd love to call an official VOTE. Please VOTE about moving Apache OpenJPA to GIT. More precisely the preferable option of gitbox. Albeit this is some minor question as a GIT repo can be moved

Re: [VOTE] move Apahe OpenJPA from SVN to gitbox hosted at ASF

+1 Em ter, 9 de out de 2018 às 13:01, Jonathan Gallimore < jonathan.gallim...@gmail.com> escreveu: > +1 > > On Tue, Oct 9, 2018 at 4:25 PM Mark Struberg > wrote: > > > hi folks! > > > > Since the discuss thread showed good support I'd love to call an official > > VOTE. > > > > > > Please VOTE

Re: [VOTE] move Apahe OpenJPA from SVN to gitbox hosted at ASF

+1 On Tue, Oct 9, 2018 at 4:25 PM Mark Struberg wrote: > hi folks! > > Since the discuss thread showed good support I'd love to call an official > VOTE. > > > Please VOTE about moving Apache OpenJPA to GIT. More precisely the > preferable option of gitbox. Albeit this is some minor question as

Re: [VOTE] move Apahe OpenJPA from SVN to gitbox hosted at ASF

+1 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: [VOTE] move Apahe OpenJPA from SVN to gitbox hosted at ASF

+1 On Tue, 9 Oct 2018 at 22:25, Mark Struberg wrote: > hi folks! > > Since the discuss thread showed good support I'd love to call an official > VOTE. > > > Please VOTE about moving Apache OpenJPA to GIT. More precisely the > preferable option of gitbox. Albeit this is some minor question as a

[VOTE] move Apahe OpenJPA from SVN to gitbox hosted at ASF

hi folks! Since the discuss thread showed good support I'd love to call an official VOTE. Please VOTE about moving Apache OpenJPA to GIT. More precisely the preferable option of gitbox. Albeit this is some minor question as a GIT repo can be moved around without loosing any information. So it

Re: [DISCUSS] move from SVN to GIT?

Infra clearly prefers gitbox these days. And again: all our stuff is _still_ hosted on ASF hardware! gitbox is really just a more fancy mirroring to GitHub + better integration. LieGrue, strub > Am 09.10.2018 um 14:19 schrieb Romain Manni-Bucau : > > Maybe let's tackle gitbox/git wip topic

Re: [DISCUSS] move from SVN to GIT?

Maybe let's tackle gitbox/git wip topic before a vote I thought gitbox was real github repo and therefore gives github power on contribution side - agree bugtracker of github must be disabled. Can you check it Mark please? Im in a conf the whole week so not that easy but think it is the main

Re: [DISCUSS] move from SVN to GIT?

As far as I understand all cannonical git repos are still always hosted at ASF. Even for gitbox. But the integration is much tighter. And ftr: I also don't really like all the github binding. And we sill still continue to use JIRA and our ASF mailing lists etc. I'm even in favour to disable the

Re: [DISCUSS] move from SVN to GIT?

On 09/10/2018 14:08, Maxim Solodovnik wrote: We moved to gitbox since "old git asf" doesn't allow PR merging Not completely correct: you can merge PRs via git commits. Regards. On Tue, 9 Oct 2018 at 19:06, Francesco Chicchiriccò wrote: On 09/10/2018 14:03, Romain Manni-Bucau wrote: Le

Re: [DISCUSS] move from SVN to GIT?

We moved to gitbox since "old git asf" doesn't allow PR merging On Tue, 9 Oct 2018 at 19:06, Francesco Chicchiriccò wrote: > On 09/10/2018 14:03, Romain Manni-Bucau wrote: > > Le mar. 9 oct. 2018 14:33, Francesco Chicchiriccò > a > > écrit : > > > >> On 09/10/2018 13:18, Mark Struberg wrote: >

Re: [DISCUSS] move from SVN to GIT?

Le mar. 9 oct. 2018 15:06, Francesco Chicchiriccò a écrit : > On 09/10/2018 14:03, Romain Manni-Bucau wrote: > > Le mar. 9 oct. 2018 14:33, Francesco Chicchiriccò > a > > écrit : > > > >> On 09/10/2018 13:18, Mark Struberg wrote: > >>> hi folks! > >>> > >>> The OpenJPA codebase is big and

Re: [DISCUSS] move from SVN to GIT?

On 09/10/2018 14:03, Romain Manni-Bucau wrote: Le mar. 9 oct. 2018 14:33, Francesco Chicchiriccò a écrit : On 09/10/2018 13:18, Mark Struberg wrote: hi folks! The OpenJPA codebase is big and mature. That kind of cries for using feature branches for some parts. And while SVN is great

Re: [DISCUSS] move from SVN to GIT?

Le mar. 9 oct. 2018 14:33, Francesco Chicchiriccò a écrit : > On 09/10/2018 13:18, Mark Struberg wrote: > > hi folks! > > > > The OpenJPA codebase is big and mature. > > That kind of cries for using feature branches for some parts. > > And while SVN is great overall, branching is still

Re: [DISCUSS] move from SVN to GIT?

+1 Jon On Tue, 9 Oct 2018, 12:18 Mark Struberg, wrote: > hi folks! > > The OpenJPA codebase is big and mature. > That kind of cries for using feature branches for some parts. > And while SVN is great overall, branching is still problematic. > > Right now I would love to move from junit3 to 5.

Re: [DISCUSS] move from SVN to GIT?

On 09/10/2018 13:18, Mark Struberg wrote: hi folks! The OpenJPA codebase is big and mature. That kind of cries for using feature branches for some parts. And while SVN is great overall, branching is still problematic. Right now I would love to move from junit3 to 5. But that isn't possible in

Re: [DISCUSS] move from SVN to GIT?

+1 for gitbox Le mar. 9 oct. 2018 14:18, Mark Struberg a écrit : > hi folks! > > The OpenJPA codebase is big and mature. > That kind of cries for using feature branches for some parts. > And while SVN is great overall, branching is still problematic. > > Right now I would love to move from

Re: [DISCUSS] move from SVN to GIT?

+1 this will also simplify the work with PRs :) On Tue, 9 Oct 2018 at 18:18, Mark Struberg wrote: > hi folks! > > The OpenJPA codebase is big and mature. > That kind of cries for using feature branches for some parts. > And while SVN is great overall, branching is still problematic. > > Right

[DISCUSS] move from SVN to GIT?

hi folks! The OpenJPA codebase is big and mature. That kind of cries for using feature branches for some parts. And while SVN is great overall, branching is still problematic. Right now I would love to move from junit3 to 5. But that isn't possible in one commit. It needs some branch. And