+1 to move to Git. It seems it is easy for people to contribute with GIT. (Specially situations like GSOC).
Thanks Thejaka Amila On Thu, Jan 16, 2014 at 4:54 PM, Suresh Marru <[email protected]> wrote: > Thanks Marlon for resurrecting this discussion. Its also timely to the > transition before GSOC 14 and as we move towards Airavata 1.0. > > One thing we have noticed is INFRA support for GIT transition has > increased over time. Also, the integration with GITHUB, jClouds has fully > exploited this and now there may be other projects also. So all in all the > timing is very good and + 1 to move foreword for Airavata. > > Suresh > > On Jan 16, 2014, at 2:50 PM, Marlon Pierce <[email protected]> wrote: > > > Hi all-- > > > > We have discussed $subject before for other reasons without much action > > [0], so I want to bring it up again. Unless the situation has changed > > recently, Apache's Jira no longer links SVN commit messages to Jira > > tickets. For background on the issues with SVN, see [1]. This ticket > > is still unresolved. > > > > The general linking of repo commits to Jira tickets through commit > > comments [2] is a good and virtuous thing. We have lost this in > > Airavata and need to get it back. This requires moving to Git [3] [4]. > > > > What other consequences are there for doing this? Let's please > > discuss. It will take a bit of time from INFRA to make the conversion, > > but this doesn't seem to be awful. We need to preserve history if we do > > this. What else? > > > > > > Thanks-- > > > > > > Marlon > > > > [0] https://www.mail-archive.com/[email protected]/msg03881.html > > > > [1] https://ecosystem.atlassian.net/browse/SVN-385 > > > > [2] http://www.apache.org/dev/svngit2jira.html > > > > [3] https://git-wip-us.apache.org/ > > > > [4] > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20INFRA%20AND%20text%20~%20%22git%20svn%22 > >
