[
https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830594#comment-17830594
]
Bob Neugebauer commented on DERBY-7162:
---------------------------------------
Thanks [~rhillegas] . For our use of the derby codebase, I am fine with it
being a read only mirror and you ignoring forks and pull requests
As for your other questions about git mirroring, I cannot answer that myself. I
don't personally know how frequent git mirroring would occur or if there is any
involvement from the project team in that process
[~cml] This is in relation to the infra ticket I opened INFRA-25623 that you
responded to, can you let Richard know if there are impacts to the project team
if the git-mirror is updated?
Thanks
> Update Git mirror for db-derby. Current mirror is out of date, hasn't been
> updated since 2019
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-7162
> URL: https://issues.apache.org/jira/browse/DERBY-7162
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Reporter: Bob Neugebauer
> Priority: Major
>
> There is an existing GIT mirror for DB-DERBY available at
> [https://github.com/apache/derby] however this mirror is out of date. Last
> commit was Aug 2019. This mirror is missing all branches and tags that the
> derby SVN repo contains.
> I had opened an INFRA ticket INFRA-25623 to request an update to git but
> Chris said this had to come from the derby maintainers.
> I have a project that is using derby, in particular 10.17, and I am looking
> for the best way to avoid having our build servers hit ASF frequently to pull
> from SVN. Using a git fork would seem the best way to achieve this.
>
> Thanks, Bob
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
