I don't think it is worth doing another build just for this, but if there is another 3.17 build in rawhide, it would be nice to use a release in the 400s so it stays ahead of the f21 version.
Lo!
Bruno Wolff III wrote on 07.10.2014 05:07:
I don't think it is worth doing another build just for this, but if there is another 3.17 build in rawhide, it would be nice to use a release in the 400s so it stays ahead of the f21 version.
Why not move the %{?dist} to the front instead of having a numbers in the 400s there, as sooner or later we'll get to 1000 and then it will look even more ridiculous.
I know, I might sound like a broken record, as I have suggested that before. But last time it wasn't really discussed, as I was a bit late and it was mostly shot down with something like "we made a decision, we stick to that" (at least it felt like that to me and/or that's what I remember from it).
CU knurd
On Tue, Oct 07, 2014 at 07:39:24 +0200, Thorsten Leemhuis fedora@leemhuis.info wrote:
Lo!
Bruno Wolff III wrote on 07.10.2014 05:07:
I don't think it is worth doing another build just for this, but if there is another 3.17 build in rawhide, it would be nice to use a release in the 400s so it stays ahead of the f21 version.
Why not move the %{?dist} to the front instead of having a numbers in the 400s there, as sooner or later we'll get to 1000 and then it will look even more ridiculous.
That doesn't happen, because as each new upstream release is done, the numbers are reset. The most you get is 4xx (when there is a rawhide, branched and two supported releases or rawhide and three supported releases).
I know, I might sound like a broken record, as I have suggested that before. But last time it wasn't really discussed, as I was a bit late and it was mostly shot down with something like "we made a decision, we stick to that" (at least it felt like that to me and/or that's what I remember from it).
I vaguely remember that conversation, but I am pretty sure it came up that we can reset the numbers with each kernel release, so that they don't keep increasing forever.
I don't think it is worth doing another build just for this, but if there is another 3.17 build in rawhide, it would be nice to use a release in the 400s so it stays ahead of the f21 version.
Why not move the %{?dist} to the front instead of having a numbers in the 400s there, as sooner or later we'll get to 1000 and then it will look even more ridiculous.
That doesn't happen, because as each new upstream release is done, the numbers are reset. The most you get is 4xx (when there is a rawhide, branched and two supported releases or rawhide and three supported releases).
In theory it shouldn't get above the 300s, 100s for F-19, 200s for F-20, 300s for F-21 and then usually rawhide is on the next cycle. That might not be the case for the next week due to Linus travelling but it's generally unusual.
Peter
Peter Robinson wrote on 07.10.2014 12:14:
I don't think it is worth doing another build just for this, but if there is another 3.17 build in rawhide, it would be nice to use a release in the 400s so it stays ahead of the f21 version.
Why not move the %{?dist} to the front instead of having a numbers in the 400s there, as sooner or later we'll get to 1000 and then it will look even more ridiculous.
That doesn't happen, because as each new upstream release is done, the numbers are reset. The most you get is 4xx (when there is a rawhide, branched and two supported releases or rawhide and three supported releases).
In theory it shouldn't get above the 300s, 100s for F-19, 200s for F-20, 300s for F-21 and then usually rawhide is on the next cycle. That might not be the case for the next week due to Linus travelling but it's generally unusual.
Hmmm, understood, seem I had forgotten those details. I simply dislike the numbers in the hundreds and find them a bit confusing(¹), that why I jumped in :D But I can life with them, no big deal :D
CU knurd
(¹) any yes, moving the disttag to the front might look a bit odd, too
On Mon, 2014-10-06 at 22:07 -0500, Bruno Wolff III wrote:
I don't think it is worth doing another build just for this, but if there is another 3.17 build in rawhide, it would be nice to use a release in the 400s so it stays ahead of the f21 version.
We actually want it to remain below the distro versions for a very specific reason. People may choose to install kernels to get new hardware support, we do not want to make it difficult to go back to stable release kernels once the version they require has landed.
The problem of a release having a higher version than rawhide is very rare, it basically could only happen when we rebase a branched pre-release, and it will only last for a few days max. This just happens to be one of those times.
Justin
kernel@lists.fedoraproject.org
-
Bruno Wolff III -
Justin Forbes -
Peter Robinson -
Thorsten Leemhuis