currently, copr creates repo files that are hard-coded with the fedora version number, for example, from http://copr.fedoraproject.org/coprs/ryanlerch/inkscape-unstable/repo/fedora-18-i386/
it would be much better for the end-user if there was only one .repo file to download for a copr project, for example:
furthermore, would it also be possible for copr, when creating a new project, to create a "release" RPM for that project that installs the .repo file in /etc/yum.repos.d/ so a user can just install that rpm to set up the repo on their system.
We had this in past. But there was problem with EPEL repos. Because RHEL does not have in $releasever just number. It have there e.g. "6-Server" or "6-Workstation".
Which does not match with epel-6-$basearch.
So only possible solution is some heuristic in style:
if mock_chroot == "fedora"
mock_chroot == "$releasever"
ad second issue - yes, it is in plan, but if you want to track it please file another RFE. As one issue, one BZ.
logic from #1 implemented in commit 0d0b705
WebUI will still display for various Fedoras link to repo file for each Fedora, but the content will be same. And usage of $releasever will easy upgrade.
will this change current copr projects?
or will the change only be for new projects created going forward?
It will change current projects.
But after I deploy that code into production (i.e. when I close this BZ).