> > As per the Fedora 19 schedule [1], Fedora 19 Alpha Release Candidate 3 > > (RC3) is now available for testing. > > The Live spins do not have "-RC3-" in the name: > > https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/Live/i386/ > Fedora-Live-Desktop-i686-19-Alpha-1.iso 16-Apr-2013 01:40 963M > > where the expected name is > > Fedora-Live-Desktop-i686-19-Alpha-RC3-1.iso 16-Apr-2013 01:40 963M Actually this is intended, Release Candidates don't have "RC" in the file name. I find it confusing as well. I believe the reason is that "the RC that is deemed stable is not to be touched". However, I don't see a simple file-rename as a world-breaking operation. But maybe I missed some further reason? PS: The new naming style for Live images (which is now inconsistent with all other images, and not following release ordering) is terrible as well. But it's also "intended": <kparal> dgilmore: hello, I want to ask about Live.iso naming. What's the reason to change the naming standard? it is now very inconsistent with DVD and netinst.iso names <dgilmore> kparal: the reason is that koji changed how it works and we had no choice but to change it <kparal> dgilmore: can there be a single script that will rename the files into a standardized naming structure (I believe adamw proposed something a long time ago and wikified it) after the compose is complete? <kparal> it would really help those of us who want to process the iso files in an automated fashion <kparal> for example I'd like to generate pxeboot config files dynamically, but I need a stable naming scheme <dgilmore> kparal: no <kparal> that doesn't really help much <kparal> dgilmore: you still need to copy the iso files from koji to dl.fp.o, right? what if the script first renamed them and then copied them? or vice-versa? is there some technical problem with that? -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
