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-**
pull-request-on-git<http://stackoverflow.com/questions/6235379/how-to-send-pull-request-on-git>
