Ah, that has been a mistake on my part, apologies. I can use a more "correct" naming scheme in the future.
Are there any rules besides this one that release names should adhere to? I'll write up a document about it so I have it documented, and other people know what to expect as well. On Wed, 6 Nov 2019 09:35:32 -0500 Parrot Raiser <1parr...@gmail.com> wrote: > When I report a problem, I try to supply as complete a picture as > possible, without imposing my filter on the data. So many times I've > had a vital clue omitted by someone who "didn't think that X was > important". > > With so many parties involved, it's not surprising that errors reveal > issues entirely outside your ken; those capable of fixing them may see > the report and fix them. > > > I'm not sure what you mean with "-n vs .n for sub-version ids". I > > The Rakudo* convention for normal releases was YYYY.MM, for > experimental or supplemental releases was YYYY.MM-N, so my download > script inserted "-" as the separator if given a third parameter, while > you're using YYYY.MM.N I just changed the script, but again reported > it in case someone else also uses a script. -- With kind regards, Patrick Spek www: https://www.tyil.nl/ mail: p.s...@tyil.nl pgp: 1660 F6A2 DFA7 5347 322A 4DC0 7A6A C285 E2D9 8827 social: https://soc.fglt.nl/tyil git: https://gitlab.com/tyil/
pgpQO9iprHxTP.pgp
Description: OpenPGP digital signature
