We need to discuss and determine, but I was thinking breaking it up into separate repo's:
* Web site * River * tck test suite (no development). * delegates * anything else? Should we separate out the qa integration test suite? If we do, we can test binary compatibility between releases. There's lots of old experimental branches etc, should they be archived? Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Patricia Shanahan <p...@acm.org> Sent: 29/09/2016 07:35:44 pm To: dev@river.apache.org Subject: Re: Fwd: [jira] [Updated] (INFRA-12432) Apache River migration from SVN to Git - Git commit access I may have missed something, but I didn't see a proposal for dealing with the comment: "This will be complicated and time consuming as the svn repo doesn't fit the usual trunk/branches/tags format. You may want to do some consolidation or break this down into multiple git repos, for example, river-site.git, river-rt-tools.git, etc. prior to us doing an SVN->Git migration. If you'd rather have it all in one repo, let us know and we'll see what we can do." What is the response to this? On 9/29/2016 12:39 AM, Peter wrote: > Are there any remaining objections to git migration? > > If so, lets discuss. > > Regards, > > Peter. > > Sent from my Samsung device. > > Include original message > ---- Original message ---- > From: Daniel Takamori (JIRA) <j...@apache.org> > Sent: 29/09/2016 03:52:20 am > To: j...@zeus.net.au > Subject: [jira] [Updated] (INFRA-12432) Apache River migration from SVN to >Git - Git commit access > > > [ >https://issues.apache.org/jira/browse/INFRA-12432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Daniel Takamori updated INFRA-12432: > ------------------------------------ > Status: Waiting for user (was: Waiting for Infra) > >> Apache River migration from SVN to Git - Git commit access >> ---------------------------------------------------------- >> >> Key: INFRA-12432 >> URL: https://issues.apache.org/jira/browse/INFRA-12432 >> Project: Infrastructure >> Issue Type: New Git Repo >> Components: Git >> Reporter: Peter Firmstone >> > > > >
