I haven't received any feedback on the patches or the PR, I therefore defer migration for one week. Please have a look at https://issues.apache.org/jira/browse/OAK-9440 <https://issues.apache.org/jira/browse/OAK-9440> and the attached patches and PR
Thanks, Konrad > On 2. Jun 2021, at 16:59, Konrad Windszus <konra...@gmx.de> wrote: > > Hi, > Here are some updates regarding the migration: > > 1) I provided a (draft) PR in > https://github.com/apache/jackrabbit-oak/pull/296 with the necessary fixes > for the Oak source code and the Oak documentation site. Please have a look. > > 2) For http://jackrabbit.apache.org/jcr/creating-releases.html there is a > patch attached to https://issues.apache.org/jira/browse/OAK-9440 > > 3) For https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh > there is a patch attached to https://issues.apache.org/jira/browse/OAK-9440 > as well. > > 4) I would propose to get rid of https://jackrabbit.apache.org/oak/index.html > and instead just redirect to > https://jackrabbit.apache.org/oak/docs/index.html as the latter provides all > relevant information and the former is really manually maintained HTML > AFAICS. Please tell me in case you think the HTML at > https://jackrabbit.apache.org/oak/index.html is worth keeping. > > Is there anything else which I might have missed? > > Konrad > > >> On 25. May 2021, at 18:42, Konrad Windszus <konra...@gmx.de> wrote: >> >> 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 <konra...@gmx.de> 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 >> >
