[
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-4979:
---------------------------------
Description:
In order to foster contribution and ease switching between
branches/cherrypicking and in general to have a modern development workflow I
propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was
done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit
FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
It would comprise of the following steps:
# migrate the SVN repository at
https://svn.apache.org/repos/asf/jackrabbit/branches,
https://svn.apache.org/repos/asf/jackrabbit/trunk and
https://svn.apache.org/repos/asf/jackrabbit/tags to a Git repository named
"jackrabbit" (hosted at https://gitbox.apache.org/repos/asf)
# migrate GitHub SVN mirror at https://github.com/apache/jackrabbit to mirror
the new native Git repo (at Gitbox)
# make the SVN repository at the folders outlined at 1. read only
# adjust documentation
# adjust check script
# adjust Jenkins Jobs
https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk and
https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/
VOTE thread in https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj
was:
In order to foster contribution and ease switching between
branches/cherrypicking and in general to have a modern development workflow I
propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was
done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit
FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
It would comprise of the following steps:
1. migrate the SVN repository at
https://svn.apache.org/repos/asf/jackrabbit/branches,
https://svn.apache.org/repos/asf/jackrabbit/trunk and
https://svn.apache.org/repos/asf/jackrabbit/tags to a Git repository named
"jackrabbit" (hosted at https://gitbox.apache.org/repos/asf)
2. migrate GitHub SVN mirror at https://github.com/apache/jackrabbit to mirror
the new native Git repo (at Gitbox)
3. make the SVN repository at the folders outlined at 1. read only
VOTE thread in https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj
> Migrate from Subversion to Git
> ------------------------------
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> In order to foster contribution and ease switching between
> branches/cherrypicking and in general to have a modern development workflow I
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
> # migrate the SVN repository at
> https://svn.apache.org/repos/asf/jackrabbit/branches,
> https://svn.apache.org/repos/asf/jackrabbit/trunk and
> https://svn.apache.org/repos/asf/jackrabbit/tags to a Git repository named
> "jackrabbit" (hosted at https://gitbox.apache.org/repos/asf)
> # migrate GitHub SVN mirror at https://github.com/apache/jackrabbit to mirror
> the new native Git repo (at Gitbox)
> # make the SVN repository at the folders outlined at 1. read only
> # adjust documentation
> # adjust check script
> # adjust Jenkins Jobs
> https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk and
> https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/
> VOTE thread in
> https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
