I'm not sure what this is trying to solve. The current versioning scheme is used to reflect that the next version is not release yet. Changing it to use the version number of the release that is being developed seems odd to me, but I'm not entirely opposed.

I would like to know exactly why the proposer thinks the change is needed, and what it's really trying to solve though.

There I think three parts:

1. Currently the version (as opposed to just the release) changes as rawhide progresses. So if you want to use $releasever in repo files, you have to much with things a couple of times during rawhide instead of just once at the branch.

2. The version is not an integer. This makes rawhide special. I think we should be making rawhide less special.

3. I don't think the version reflects which release of Fedora you are using very well. You are really running a prerelease of the next release, rather than a postrelease of the currently released Fedora. And hence I think using version-release naming along the lines used for the kernel makes more sense.

I don't think this is going to be a big improvement over the current situation, but I think it is a little better. However there are costs to doing this (Woods mentioned there is stuff that does special things with *.9? versions) and right now I don't know what processes need to be tweaked. It's not just changing the version used for fedora-release. Another issue is the possibility for more confusion. Are people used to seeing X-0.Y and knowing that that designates a prerelease of version X?

This was postponed until rel-eng can think about the implementation further. Removing from agenda, but leaving ticket open.

It looks like this has been implemented as there is a fedora-release-13-0.1 .