[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829946#comment-17829946 ] Richard N. Hillegas commented on DERBY-7162: Apache Derby is an old project maintained by old engineers who use old tools. Our code is maintained in subversion. None of the active committers accept contributions via git. I don't remember who created this git mirror. Clearly no-one volunteered to keep it evergreen. That said, I have no objection to periodic, automatic updates of this git mirror provided that 1) I don't have to do anything more than make one request to INFRA to make it so. 2) It is understood that the Derby project considers this to be a read-only mirror. 3) It is further understood that the Derby project will ignore this mirror and all forks from it. If that is an acceptable situation, then I will need someone to tell me what I need to do to enable it. -Rick > 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)
[jira] [Updated] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Neugebauer updated DERBY-7162: -- Issue Type: Task (was: Bug) > 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)
[jira] [Created] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
Bob Neugebauer created DERBY-7162: - Summary: 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: Bug Components: Build tools Reporter: Bob Neugebauer 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)
