Hi,
The migration (tracked in https://issues.apache.org/jira/browse/JCR-4979) is
done now.
I.e. the old SVN repository locations are read only. Please only the Git
repository from now on hosted at https://github.com/apache/jackrabbit /
https://gitbox.apache.org/repos/asf/jackrabbit.git
If you h
[X] +1, migrate Jackrabbit to Git
Regards
Julian
On Thu, Oct 12, 2023 at 6:57 AM Julian Reschke wrote:
>
> On 12.10.2023 06:55, Julian Reschke wrote:
> > On 11.10.2023 19:58, Konrad Windszus wrote:
> >> ...
> >
> > [X] +1, migrate Jackrabbit to Git
> >
> > Best regards, Julian
>
> ...and when we
On 11.10.23, 20:00, "Konrad Windszus" wrote:
> [..] I propose to migrate Jackrabbit (Classic) from SVN to Git [..]
+1, migrate Jackrabbit to Git
Regards
Marcel
On 12.10.2023 06:55, Julian Reschke wrote:
On 11.10.2023 19:58, Konrad Windszus wrote:
...
[X] +1, migrate Jackrabbit to Git
Best regards, Julian
...and when we get to it, please be consistent with Oak (in naming the
dev branch "trunk").
Best regards, Julian
On 11.10.2023 19:58, Konrad Windszus wrote:
...
[X] +1, migrate Jackrabbit to Git
Best regards, Julian
+1
Woonsan
On Thu, Oct 12, 2023 at 3:00 AM Konrad Windszus wrote:
>
> Hi,
> 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
[ ] +1, migrate Jackrabbit to Git
Thanks
Rishabh Daim
On Wed, 11 Oct, 2023, 11:28 pm Konrad Windszus, wrote:
> Hi,
> 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 (Classi
Hi,
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
