+1 for moving to git. For the svn maven repo, I just have a quick look the artifacts, I don't think we need them any more.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thursday, March 28, 2013 at 9:45 PM, Hadrian Zbarcea wrote: > Inline. > Hadrian > > On 03/28/2013 09:35 AM, Daniel Kulp wrote: > > > > On Mar 28, 2013, at 4:26 AM, Christian Müller <christian.muel...@gmail.com > > (mailto:christian.muel...@gmail.com)> wrote: > > > > > Hadrian, it looks like your timing is better than my one [1] ;-) > > > > > > In general, I'm +1 to switch to Git (I use git-svn at Camel since I can > > > remember...). > > > > > > It's not clear for me right now what we have to do with the projects which > > > are not located under trunk [2] - [6]. I don't think we need all of them. > > > But what's with our sandbox project/module? Do we have to move it into > > > trunk? > > > > > > [1] > > > http://camel.465427.n5.nabble.com/DISCUSS-force-switching-from-SVN-to-GIT-td5715773.html > > > [2] https://svn.apache.org/repos/asf/camel/scripts/ > > > > > > > > These could just go in trunk/release_scripts or something. Either that or > > just thrown away. The publish_camel_distro.sh > > (http://publish_camel_distro.sh) script certainly is wrong now. > Not used in ages. Relics from camel as an activemq subproject. New > working versions exist at: > https://svn.apache.org/repos/asf/camel/trunk/etc/scripts/ > > > > > > [3] https://svn.apache.org/repos/asf/camel/website/ > > > > This would likely need to stay for now. > Right > > > > > > [4] https://svn.apache.org/repos/asf/camel/sandbox/ > > > > No idea on this. > Not needed imho, because with git/github there are other ways to > collaborate and share. Again, imho. > > > > > > [5] https://svn.apache.org/repos/asf/camel/m2-repo/ > > > > I hope this isn't actually being used. If it is, this needs to be fixed > > ASAP. I think INFRA has announced in may that all the "m2-repo" things in > > svn will be disabled in May. If there is anything left in there that is > > needed, it NEEDS to get pushed to central. > Not needed anymore, afaik, but will check to make sure. In any event, if > used, it must be resolved asap, regardless of a move to git. > > > > > > [6] https://svn.apache.org/repos/asf/camel/ide/ > > > > Discarded. Has been touched in 5 years. > True. > > > > > All of this remains in SVN's history forever so not a big deal. If we ever > > need any of it back, it will always be there. > > > > Dan > > > > > > > > > > Best, > > > Christian > > > > > > On Wed, Mar 27, 2013 at 9:01 PM, Hadrian Zbarcea <hzbar...@gmail.com > > > (mailto:hzbar...@gmail.com)> wrote: > > > > > > > Would that something that sounds appealing to most? I think most of us > > > > already use mostly git anyway. The ASF infra now offers the choice. > > > > > > > > Same question goes about camel-extra, I opened an issue there [1] and as > > > > much as I dislike bringing that on this list, well, I did it for lack > > > > of a > > > > better forum. > > > > > > > > [1] http://code.google.com/a/**apache-extras.org/p/camel-** > > > > extra/issues/detail?id=38<http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=38> > > > > > > > > -- > > > > Hadrian Zbarcea > > > > Principal Software Architect > > > > Talend, Inc > > > > http://coders.talend.com/ > > > > http://camelbot.blogspot.com/ > > > > > >
