www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11056) Migrate Lucene project from SVN to Git.
Date Tue, 19 Jan 2016 10:04:40 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106532#comment-15106532
] 

Daniel Gruno commented on INFRA-11056:
--------------------------------------

If we reset the current repo, please be aware that any pull requests etc you may have will
be removed. We can't just "replace" the repo and have the PRs still be there.
If you are fine with this, we'll nuke the two existing repos and set up two new empty ones.

> Migrate Lucene project from SVN to Git.
> ---------------------------------------
>
>                 Key: INFRA-11056
>                 URL: https://issues.apache.org/jira/browse/INFRA-11056
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git
>            Reporter: Mark Miller
>            Assignee: Daniel Gruno
>
> The Lucene project was recently notified that our strategy for mirroring to Git from
SVN was not sustainable. As a result, the project has decided to move from SVN to Git.
> Some committers had an issue with how large our history was in Git for various reasons,
and so we have produced a cleaned up repo for our use.
> Relevant issues:
> LUCENE-6937: Migrate Lucene project from SVN to Git.
> LUCENE-6933: Create a (cleaned up) SVN history in git.
> We would like to take our cleaned up Git repo in LUCENE-6933 and move to it from our
Apache SVN location.
> One of our subprojects, PyLucene, is happy to stick with it's spot in SVN. I think we
probably want to make the rest of our SVN location read-only.
> Other Lucene committers will likely comment in further detail as necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message