On 10 March 2013 07:18, Lewis John Mcgibbney <[email protected]> wrote: > Hi Peter, > Please see my comments inline... > > On Tue, Mar 5, 2013 at 11:03 AM, <[email protected]> wrote: > >> >> Move to Git >> 2454 by: Peter Ansell >> >> The infrastructure team would like the PPMC to confirm that the Git >> repository is an accurate copy of the Subversion directory. >> >> There are quite a few non-standard directories in the Subversion >> repository and we need to confirm that they do not need to be in the >> Git repository. >> >> Some of the directories have been referenced in Jira issues so far: >> >> * /repo/ - ANY23-61 >> * /sandbox/ - ANY23-60 >> * /repo-ext/ - ANY23-56 >> > > We DO NOT need these in the git repos > > >> >> The other directories include: >> >> * /site/ : Does svnpubsub use this? [1] >> > > AFAIK yes.
Then we will need to sort this out. >> * /wiki/ : Not sure about where this one is used. >> > > This is legacy and was for Any23 prior to it being proposed to the Apache > Incubator. We DO NOT need this is git > > >> * /committers/ : Is there another way of keeping this information around? >> > > Unless we pull it in to trunk then no. I think it is good to have this > stuff separated out into its own directory. Is there a problem having this > taken into Git repo? There isn't a problem as such, but it isn't there right now. >> >> Once we decide what is happening to those directories we can start a >> vote to formally confirm that the Git repository is an accurate copy >> of the subversion directories and start using it as the main >> repository. >> > > In principle this sounds great. I'm just not sure how many VOTE's we will > get!!! I am happy to take this forward. I don't want unnecessary votes, but the infrastructure team need to have an indication that we accept the new repository as accurate. The previous vote was to move in principle to Git, without details like the svnpubsub changes etc. Once we sort out the svnpubsub issue and the external repository (see below), we will be in a position to vote and then change over. >> If necessary, the website directories can be added as separate >> branches in Git which never get merged with the code branches, in the >> same way that on GitHub Project Pages use the "gh-pages" branch to >> publish their websites [2]. Not sure about how svnpubsub would work >> with that if we are using it though. >> >> Neither do I actually. > Another thing which we really need to confirm... how the hell do releases > work? The main pom.xml is hard configured with the following properties > which point to SVN > > developerConnection This should be simple to change. > site.deploymentBaseUrl Not sure what this one should change to. > any23-repository-external The csv utils artifact in any23-repository-external needs to be dealt with, either by deploying it to Maven Central, or getting the upstream to do a patched release (or by temporarily including the patched upstream library source code in the any23-csvutils module). Peter
