(Replying as the one who came up with the original name) Not sure current name is that good, but imo we should not rename - main reason is that we might eventually add upstream support one day, and it will then be ugly if we now rename. I do not think it causes that much confusion - does it? We do not package for upstream, so whoever that looks at it upstream must do this by first looking at the source. Perhaps we should patch README to clarify that it currently only supports RHV, and that patches for oVirt are welcome :-) On Sun, May 27, 2018 at 7:59 AM, eyal edri (oVirt JIRA) < jira@ovirt-jira.atlassian.net> wrote:

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36668#comment-36668 ]

eyal edri commented on OVIRT-2058:

I'm not sure it's a good idea to name upstream project rhvm just for consistency, there are other projects which have this diff between upstream and downstream.

Maybe you meant ovirt-fast-forward-upgrade?

Also, I'm not sure it's possible to rename a git repo, we probably need to create new one and repush all content.

On Fri, May 25, 2018, 19:16 Douglas Landgraf (oVirt JIRA) <

rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade

Key: OVIRT-2058 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2058 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Douglas Landgraf Assignee: infra

Hi, Please rename project ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade in gerrit and related components. Reason: project name consistency Thanks! — Cheers Douglas

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org

-- Didi