Hi Dan,
This one:
http://svn.apache.org/viewvc/river/ldj-tests/
I considered a single svn git move, it would certainly simplify the
process on our part, the cost is that people looking at the repository
on github will need to dig through the directory structure to find the
development code, or build the project. Having said that, I would say
that doers decide, we're short on resources and we could do a single
move now and break it up later.
Cheers,
Peter.
On 16/02/2021 5:44 am, Dan Rollo wrote:
Hi Peter,
Silly questions to follow.
I found the empty repo at: river-ldj-tests.git
<https://git.apache.org/repos/asf/river-ldj-tests.git>
(https://git.apache.org/repos/asf/river-ldj-tests.git
<https://git.apache.org/repos/asf/river-ldj-tests.git>)
As a sanity check: Is the one to migrate
from?: http://svn.apache.org/repos/asf/river/jtsk/trunk
While I agree refactoring of the project structure into separate,
stand alone git repos would be an improvement, I’m wondering if a
safer first step would be to move the svn repo to git as is? That way,
we start from a working state in git, and preserve all the svn
history. From there, we can start to “break things” (literally and
figuratively) into smaller repos. The underlying assumption is just
about everything will be easier to do (merging, etc) with a git repo.
Either way, I’ll start looking for lines along which I could break things.
Dan
On Feb 9, 2021, at 3:42 AM, Peter Firmstone
<peter.firmst...@zeus.net.au <mailto:peter.firmst...@zeus.net.au>> wrote:
Thanks Dan,
https://infra.apache.org/svn-to-git-migration.html
<https://infra.apache.org/svn-to-git-migration.html>
https://gitbox.apache.org/setup/newrepo.html
http://svn.apache.org/viewvc/river/
https://gitbox.apache.org/repos/asf#river
I just created a git repository for the "Apache river JiniTM
Technology Lookup, Discovery, and Join Compatibility Kit", I figure
it might be easier to start with something that's had relatively few
commits as an experiment.
But basically everything we have on svn needs to be broken up into
separate projects, typical of what people are used to seeing on github.
The QA test suite is an ant build project, it's currently part of
trunk, but I was thinking of separating it out into it's own build.
On 9/02/2021 12:31 pm, Dan Rollo wrote:
Hi Peter,
I’m apologize for not being more help. I haven’t had much time of
late. Is there a thread I could pull regarding the Git migration?
Where to start?
The plan you itemize makes sense to me.
Dan Rollo
On Feb 8, 2021, at 8:35 PM, Peter Firmstone
<peter.firmst...@zeus.net.au> wrote:
Hello River folk,
There's an upcoming board report due shortly, I wanted to gauge
people's interest in the project.
We've got two pending tasks:
1. SVN to Git Migration
2. Website migration
Following the Git Migration, the plan is to continue with the
modular build, using gradle?
Lately we don't have a lot of participation, I was hoping that we
would have some more buy in, especially with the Git migration.
I don't want to be making decisions alone, are there people on this
list who have time to assist, are willing to assist or intend to do
so in future when they have time?
--
Regards,
Peter Firmstone
--
Regards,
Peter Firmstone
