To be honest, my reluctance to switch is the learning curve. I have a couple of projects that I work on in GitHub and I have had problems taking the correct action at the correct time (that is 'user error'). I guess I am just an old guy and don't really want to learn yet another tool. Then again, perhaps I need a better Eclipse Git plugin.
Claude On Tue, Aug 13, 2013 at 6:25 PM, Andy Seaborne <[email protected]> wrote: > On 13/08/13 17:09, Rob Vesse wrote: > >> I too would like to move to git though I think this should be post next >> release (whenever that is) >> > > Absolutely. This is a [Discuss] on the principle. > > > git definitely makes it easier for people to contribute to projects, and >> lightweight branches reduce the size of repos substantially making it much >> faster to do a clone (svn checkout of the full Jena tree takes forever) >> >> +1 to Holgers point about preserving commit history though I assume Infra >> would probably do the appropriate conversion for us >> > > Yes+yes > > I believe history is preserved (we kept the CVS history from SF!) > Infra have to do the core move itself. > > Andy > > > >> Rob >> >> On 8/13/13 1:35 AM, "Andy Seaborne" <[email protected]> wrote: >> >> I would like to migrate to git. >>> >>> 1/ For people contributing to the project, I think it makes it easier >>> for them to work using clone-branch-push/patch [1] >>> >>> 2/ For the project, I think it makes it easier for us to work on and >>> record what has been changed by using the light-weight branching, rather >>> than just commits to trunk. >>> >>> Many changes are small, for example, JIRA fixes. We don't seem to use >>> svn branches; my experience of them is that they are cumbersome and not >>> worth the cost for small changes. >>> >>> 3/ We're already receiving git style patches. >>> >>> Andy >>> >>> [1] "git request-pull" >>> >>> On 11/08/13 17:36, Claude Warren wrote: >>> >>>> I would like to stay on SVN. >>>> >>>> >>>> On Sun, Aug 11, 2013 at 5:17 PM, Andy Seaborne <[email protected]> wrote: >>>> >>>> What are everyone thoughts on migrating to Apache git as the primary >>>>> SCM >>>>> for Jena? >>>>> >>>>> There is already a mirror on github: https://github.com/apache/jena >>>>> >>>>> And there is >>>>> >>>>> git://git.apache.org/jena.git >>>>> >>>>> - I don't know what that is; some sort of mapping from svn (live? >>>>> mirrored?) >>>>> >>>>> The migration process isn't zero-work, judging by reading around other >>>>> projects. >>>>> >>>>> 1/ It takes time and the svn repo is read-only for a period. >>>>> We'll need to make sure a release isn't likely. >>>>> >>>>> 2/ The build process doc needs updating (and checking!) >>>>> >>>>> 3/ The web site needs updating >>>>> >>>>> 4/ We all have to change our personal workflows. >>>>> >>>>> 5/ It's not github. >>>>> >>>>> The website stays in SVN (pubsub and CMS only work with SVN currently). >>>>> >>>>> Andy >>>>> >>>>> PS >>>>> http://stackoverflow.com/****questions/6235379/how-to-send-****<http://stackoverflow.com/**questions/6235379/how-to-send-**> >>>>> >>>>> pull-request-on-git<http://**stackoverflow.com/questions/** >>>>> 6235379/how-to-se<http://stackoverflow.com/questions/6235379/how-to-se> >>>>> nd-pull-request-on-git> >>>>> >>>>> >>>>> >>>> >>>> >>> >> > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> Identity: https://www.identify.nu/[email protected] LinkedIn: http://www.linkedin.com/in/claudewarren
