[Test-Announce] naming schemes

[Kamil Paral]

> > If I knew why someone thought 21_Alpha_TC6 was better than F21a-TC1 and
> > 21-Alpha-TC3 I could do better. I never put underscores or whitespace in
> > filenames or directory names. Names of downloads that do either get trashed
> > or renamed. What's wrong with 21AlphaTC6, kdeRuntimeLibs or
> > googleDroidSansMonoFonts, all of which can be pronouced without a bazillion
> > extra syllables? Un-der-score, multiply? Why does anyone do that? Can
> > anyone
> > type an underscore without looking at the keyboard? Underscores for most
> > purposes (not all), are _booby_traps_ (only after clicking send will I know
> > if they produced the result I want).
> 
> To separate the individual elements, so you can parse the string
> reliably. In the string 21AlphaTC6 how do I know where the release
> number stops and the milestone starts and the milestone stops and the
> compose type starts, without a lot of hardcoded special sauce knowledge
> in the parser? The function of the - and/or _ are to act as separators
> to make parsing the string easier and more reliable.

If the intent is to make the compose dir machine-processable, the best idea would be to add something like .composeinfo file inside the directory, which would contain all the metadata in a ini-style or json-style syntax.

[global]
release=21
milestone=Alpha
compose=TC1
arches=x86_64,i386,armhfp

[workstation x86_64]
location_parent=Workstation/
location_live=Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Alpha-TC7.iso
location_netinst=Workstation/x86_64/iso/Fedora-Workstation-netinst-x86_64-21_Alpha_TC7.iso

[server x86_64]
server_location=Server/
...

Oh how much I would love that.