Git migration

[Peter Firmstone <pe...@zeus.net.au>]

Hello River folk,

Just an update on progress, the git mirror was out of date, it has been 
deleted to clear the way for copying our current SVN.

https://issues.apache.org/jira/browse/INFRA-21216?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

Also I think it would be cleaner to have separate git repositories for 
separate components, such as the ldj test suite or other contributions 
that aren't part of the main release, so that River is easier for new 
users to become familiar with, rather than having a super repository 
that contains all components as SVN does currently.

I welcome suggestions as to how the git repositories should be structured.

-- 
Regards,
  
Peter Firmstone
0498 286 363
Zeus Project Services Pty Ltd.

Re: Git migration

[Peter Firmstone <pe...@zeus.net.au>]

Thanks Gregg,

Something that's been in the back of my mind also is the qa test suite, 
whether this should be a separate binary build, so that binary 
compatibility can also be tested between releases.

I agree with your sentiment here, it would be nice to streamline and 
make what we have easier to understand.

Information on the migration is pretty light on at the moment, there's a 
tool to get the branches structured properly.

https://infra.apache.org/svn-to-git-migration.html

Cheers,

Peter.

On 19/01/2021 2:10 pm, Gregg Wonderly wrote:
> I think that separate repositories is a good idea.  It might be interesting for one of those repositories to require a specific layout of the repositories and provide a script to “pull” all the correlated versions etc.  I sometimes struggle with all the variations on how this gets done.  At some place we need to pull all the details into view in a way that is also “easy” to consume.
>
> Gregg
>
>> On Jan 18, 2021, at 4:44 PM, Peter Firmstone <pe...@zeus.net.au> wrote:
>>
>> Hello River folk,
>>
>> Just an update on progress, the git mirror was out of date, it has been deleted to clear the way for copying our current SVN.
>>
>> https://issues.apache.org/jira/browse/INFRA-21216?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>>
>> Also I think it would be cleaner to have separate git repositories for separate components, such as the ldj test suite or other contributions that aren't part of the main release, so that River is easier for new users to become familiar with, rather than having a super repository that contains all components as SVN does currently.
>>
>> I welcome suggestions as to how the git repositories should be structured.
>>

Re: Git migration

[Gregg Wonderly <ge...@cox.net>]

I think that separate repositories is a good idea.  It might be interesting for one of those repositories to require a specific layout of the repositories and provide a script to “pull” all the correlated versions etc.  I sometimes struggle with all the variations on how this gets done.  At some place we need to pull all the details into view in a way that is also “easy” to consume.

Gregg

> On Jan 18, 2021, at 4:44 PM, Peter Firmstone <pe...@zeus.net.au> wrote:
> 
> Hello River folk,
> 
> Just an update on progress, the git mirror was out of date, it has been deleted to clear the way for copying our current SVN.
> 
> https://issues.apache.org/jira/browse/INFRA-21216?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> 
> Also I think it would be cleaner to have separate git repositories for separate components, such as the ldj test suite or other contributions that aren't part of the main release, so that River is easier for new users to become familiar with, rather than having a super repository that contains all components as SVN does currently.
> 
> I welcome suggestions as to how the git repositories should be structured.
> 
> -- 
> Regards,
> Peter Firmstone
> 0498 286 363
> Zeus Project Services Pty Ltd.
>