The vote passes with the following result: +1 (binding): Marcel, Matt and myself.
I propose to do the change in CW 24 (14th -18th of June). That should give us all enough time to prepare for the switch (which is done by ASF INFRA). Since the SVN will stay (with read-only access) we shouldn't break any downstream build jobs. But those will obviously only get the new changes once they switch to Git. No need to do it in a big bang though, so hopefully agreeing on a week is enough (as it is hard to align with INFRA on one specific day) I am gonna prepare PRs already for documentation updates and the necessary changes for the pom.xmls, so everyone can review prior to the migration and we can merge them afterwards. Konrad > On 19. May 2021, at 09:24, Konrad Windszus <[email protected]> wrote: > > Hi, > in > https://lists.apache.org/thread.html/8ea0d827d9e8488183648f2364ecd4e178b6d82e03193735aae6b5cd%40%3Coak-dev.jackrabbit.apache.org%3E > we discussed moving to Git. After the successful migration of FileVault to > Git we should tackle Oak as well. > I am volunteering to trigger the actual work (mostly on ASF INFRA side). I > hereby propose to > > 1. migrate the SVN repository at > https://svn.apache.org/repos/asf/jackrabbit/oak/ to a Git repository named > "jackrabbit-oak" > 2. migrate GitHub SVN mirror at https://github.com/apache/jackrabbit-oak to > mirror the new native Git repo (at Gitbox) > 3. change the main branch name from "trunk" to "main" > 4. make the SVN repository read only > > Vote is open for 72 hours. > [ ] +1, migrate Oak to Git > [ ] 0 > [ ] -1, because... > > > The actual work is tracked in https://issues.apache.org/jira/browse/OAK-9440. > > Thanks, > Konrad
