User:Bruno/Sane Versioning for fedora-release
From FedoraProject
Contents |
Overview
Currently in rawhide, the version of fedora-release changes a few times during a development cycle. Having just the release change instead, would simplify scripting and the use of repo files.
Problem Space
By keeping the version constant (and preferably just an integer corresponding to the upcoming release) during the process, the $releasever variable would be usable in repo files. Other scripts would be shareable between rawhide and normal releases if the version of fedora-release was used in a consistant manner.
Solution Overview
When rawhide is branched for the next release a fedora-release package is created with a version matching the next release and a release of 0.1 is used. If other releases are made during the development cycle, the integer after the . is increased by 1.
Scope
There are some process that pull meaning from .9x versions. Those would have to be found and changed to still work.
Active Ingredients
Finding the processes that depending on the current rawhide versioning scheme and fix them.
Discussion Points
How do we look for these? Are there a few people that would just know?
Comments ?
- Bruno: Related to this and to where I would like to see things go, is that in the repos that rawhide would be accessible as releases/nn (where nn is the next release number) and that updates and updates-testing repos would exist (though just contain meta-data). These would be created at the branch point. By doing things this way, you no longer need the rawhide repo files. Once you upgrade to the rawhide version of fedora-release, further updates would come from the rawhide reops. I have also requested a change to yum to make it easy to refer to specific release versions, so that grabbing the next fedora-release package could be made easy.
