Shouldn't the Fedora ISOs be named: Fedora-20-Beta-TC1-x86_64-DVD.iso rather than: Fedora-20-Beta-x86_64-DVD.iso
I notice that the spin and live ISOs are all named "Beta-TC1" rather than just "Beta"
Yes, I know, a nit.
Gene
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 03 Oct 2013 10:47:35 -0400 Gene Czarcinski gene@czarc.net wrote:
Shouldn't the Fedora ISOs be named: Fedora-20-Beta-TC1-x86_64-DVD.iso rather than: Fedora-20-Beta-x86_64-DVD.iso
I notice that the spin and live ISOs are all named "Beta-TC1" rather than just "Beta"
Yes, I know, a nit.
Gene
Its a side effect of redoing the compose processes, i need to fix it so it has -TC2 etc
Dennis
On 3 October 2013 08:47, Gene Czarcinski gene@czarc.net wrote:
Shouldn't the Fedora ISOs be named: Fedora-20-Beta-TC1-x86_64-DVD.**iso rather than: Fedora-20-Beta-x86_64-DVD.iso
I notice that the spin and live ISOs are all named "Beta-TC1" rather than just "Beta"
Yes, I know, a nit.
Not a nit, a misunderstanding. All Test Candidates are prominently named TCn with the version number as 1. Only at the Release candidate stage does the extra letters go away.
Gene
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.**org/mailman/listinfo/testhttps://admin.fedoraproject.org/mailman/listinfo/test
On Thu, 2013-10-03 at 11:20 -0600, Stephen John Smoogen wrote:
On 3 October 2013 08:47, Gene Czarcinski gene@czarc.net wrote: Shouldn't the Fedora ISOs be named: Fedora-20-Beta-TC1-x86_64-DVD.iso rather than: Fedora-20-Beta-x86_64-DVD.iso
I notice that the spin and live ISOs are all named "Beta-TC1" rather than just "Beta" Yes, I know, a nit.
Not a nit, a misunderstanding. All Test Candidates are prominently named TCn with the version number as 1. Only at the Release candidate stage does the extra letters go away.
No, his point is that that's how it *should* be, but for TC1, doesn't appear to be the case - the DVD and netinst images are named as if they were RCs.
On 3 October 2013 12:23, Adam Williamson awilliam@redhat.com wrote:
On Thu, 2013-10-03 at 11:20 -0600, Stephen John Smoogen wrote:
On 3 October 2013 08:47, Gene Czarcinski gene@czarc.net wrote: Shouldn't the Fedora ISOs be named: Fedora-20-Beta-TC1-x86_64-DVD.iso rather than: Fedora-20-Beta-x86_64-DVD.iso
I notice that the spin and live ISOs are all named "Beta-TC1" rather than just "Beta" Yes, I know, a nit.
Not a nit, a misunderstanding. All Test Candidates are prominently named TCn with the version number as 1. Only at the Release candidate stage does the extra letters go away.
No, his point is that that's how it *should* be, but for TC1, doesn't appear to be the case - the DVD and netinst images are named as if they were RCs.
My apologies to everyone. I have clearly failed 4th grade English comprehension.
Adam Williamson <awilliam <at> redhat.com> writes:
No, his point is that that's how it *should* be, but for TC1, doesn't appear to be the case - the DVD and netinst images are named as if they were RCs.
BTW, the same name issue appears when booting the install images - they are named "20-Beta", instead of "20-Beta-TC1". How important is it to name the TCs differently? It seems like just a user convenience (and a hassle for whoever does the compose), and the RCs are named identically in any case, so the user still has to be careful. I put each compose in a separate directory, with ISOs named the same as in the corresponding CHECKSUM file, so they can be verified with "sha256sum -c *-CHECKSUM", and I tell them apart by directory. It doesn't help me much to have the TCs, but not the RCs, named uniquely.
In principle it would be nice if both TCs and RCs were named uniquely, but I realize it would be even more of a hassle to rename the RC and recreate/edit the checksum file when one is picked as Gold.
On Thu, 3 Oct 2013 20:15:01 +0000 (UTC) Andre Robatino robatino@fedoraproject.org wrote:
BTW, the same name issue appears when booting the install images - they are named "20-Beta", instead of "20-Beta-TC1". How important is it to name the TCs differently? It seems like just a user convenience (and a hassle for whoever does the compose), and the RCs are named identically in any case, so the user still has to be careful. I put each compose in a separate directory, with ISOs named the same as in the corresponding CHECKSUM file, so they can be verified with "sha256sum -c *-CHECKSUM", and I tell them apart by directory. It doesn't help me much to have the TCs, but not the RCs, named uniquely.
In principle it would be nice if both TCs and RCs were named uniquely, but I realize it would be even more of a hassle to rename the RC and recreate/edit the checksum file when one is picked as Gold.
It would defeat the entire point of having a RC.
A TC can NEVER be the final released bits.
A RC could be, and if it is, it's just released. Changing it at all after it's been tested means you aren't actually testing the thing you are releasing. You are testing something else and hoping you don't mess up something in changing it.
kevin
Kevin Fenzi <kevin <at> scrye.com> writes:
On Thu, 3 Oct 2013 20:15:01 +0000 (UTC) Andre Robatino <robatino <at> fedoraproject.org> wrote:
In principle it would be nice if both TCs and RCs were named uniquely, but I realize it would be even more of a hassle to rename the RC and recreate/edit the checksum file when one is picked as Gold.
It would defeat the entire point of having a RC.
A TC can NEVER be the final released bits.
A RC could be, and if it is, it's just released. Changing it at all after it's been tested means you aren't actually testing the thing you are releasing. You are testing something else and hoping you don't mess up something in changing it.
There's no need to change the RC. For example, compose the RC exactly as it's done now, then change the ISO names to be unique. After testing, change the Gold RC's name back and recreate/edit the CHECKSUM files (for good measure make sure the checksums are the same before and after). During testing, the name is unique, and the released ISO is identical to the tested one.