naming releases

[mandville]

should we?

[RussW]

That's funny, I was only thinking that yesterday after chatting with a Aborignal (indigenous AUS people) friend and remembering the Joomla! Swahili naming convention.

I was thinking that only Major & Minor (x.y.-) releases might be named though, not the patch (-.-.z) or the dev ( x.y.z-[dev/alpha/beta/rc]) releases to save on coming up with too many names.

I certainly have nothing against the idea. Thought's on a convention?

[sozzled]

I have no idea how koori languages (there are 150+ of them) relate to Swahili? If you're talking about codenaming, it's probably a waste of time. I get the idea, you could call FPA v2.0 "Canberra" (Canberra being an aboriginal word that has one of two meanings).

I would suggest the following naming convention:

for all α, β, RC versions, these should only apply to new major/minor releases: e.g. x.0.0-alpha, x.y.0-RC, etc.

Dot-point/patch releases for after the new major/minor has become stable.

[RussW]

FPA always has, and as far as I am concerned, will continue to employ the ISO Standard Software Development/Engineering Release Management designation of major.minor.patch-devlevel, with the "devlevel" also utilising the ISO Standard designations of "dev, alpha, beta, rc".

I believe, that these designations should continue to be applied to the patch release level as well as the major & minor releases. However, from my experience, the traditional Software Development/Engineering practice is to NOT publicly offer devlevel releases that are considered to be alpha or beta except to a select list of Q&A or Test members.

This process & designation is also bourne-out by the Github framework, with the use of branches, especially the "master branch" being the alpha & beta versions (and only downloadable via the branch) whilst RC and Final revisions are available as "Official Releases".

So in essence this means that the "Releases" Tab should only ever contain RC & Final releases for download, and "alpha & beta versions can only be found in the main branch and only downloadable from there.

As far as the Release Name / Codename option, I personally still think it's a bit of fun and a lively idea, of which I also feel FPA could do with a bit of "loosening-up" & "fun value" being added to it.

[RussW]

Just thinking out-loud.... (I know, I have a bad habit of doing this and putting my foot in my mouth at the same time)

BUT... I reckon if we're going to go for this (of which I agree with @mandville and am in favour of) it should be something entertaining like;

• Old-School Cartoon Characters : Wile E. Coyote, Bugs Bunny, Roger Rabbit or something just as inane and silly, or;
• Well Known Famous Nicknames : Donk - Croc Dundee, Agent99 - Get Smart, Hot Lips - MASH, you get the picture

There's no reason for it to be serious and staid.

[mandville]

why go mainstream, an extension we use on vel is codenamed after our dogs,

[RussW]

Idea's for the naming convention?

How many dogs do you have @mandville? Enough for maybe 5-6 or more major/minor releases?

My suggestions at the moment are simply;

• Old School Cartoon Characters
• Well Known/Famous Nicknames
• Someone looks out the window and we use what they see (I see heaps of Aussie wildlife and sealife where I live)
• Stars/Constellations
• randomly pick something at the time of release

[mandville]

i have 2, fiona has 1, and why be canine, what about felines, or fishkins ?

[RussW]

My Chocolate Lab is "Georgie Girl" (after the song) and there's a "Kookaburra" (it's an Aussie bird whose call sounds like it's laughing) that visits me most days and was named "Podge" by my boys because they are cuddly little things that always look a tad on the overweight side.

[fcoulter]

I have several ex-pets as well (ie mean they have ceased to be) so no danger of running out.

The only thing about using pet names is that sometimes they are used as security questions for account recovery, maybe it is the sort of information that we should be wary of exposing. Or is that being too paranoid even for me?

[RussW]

@fcoulter, that's actually more than a fair and reasonable concern.

Let's think again, or just go with a random naming at the time of release, but that would require additional input at that time.

[fcoulter]

Or something fairly non-personal like shades of colour: beige, lilac, buttercup yellow

[mandville]

just not latin names for flowers, that would kill the 20k limit,,,

[sozzled]

If I had a preference for codenames for versions, I would use old TV westerns (although they may have "violent" connotations): e.g. Gunsmoke, Bonanza, Cheyenne, Sugarfoot, Maverick, BrokenArrow, WyattEarp, CaseyJones, Cisco (or CiscoKid), LoneRanger, Rifleman, RinTinTin, Rawhide, etc.

[fcoulter]

How about varieties of cheese? Wensleydale, Gorgonzola, Cheddar, Stilton, Camenbert?

[mandville]

I'm allergic to cheese.

On Tue, 22 May 2018, 20:23 Fiona Coulter, notifications@github.com wrote:

How about varieties of cheese? Wensleydale, Gorgonzola, Cheddar, Stilton, Camenbert?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ForumPostAssistant/FPA/issues/37#issuecomment-391111036, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2geeopNK2xT74ol86k886LPgFBAMdkks5t1GXNgaJpZM4UGfRJ .

[sozzled]

This was a big problem that I had with the Kunena project (when I was active with it). The idea was that codenames (following some theme) should be decided when development began on a new version; not at the time the new version was released to the public. While we were able to agree, generally, on the theme (although the theme changed a few times) and we were able to "vote" from some suggestions submitted within the project team, the codename was rarely seen in the code until the day the release was made public.

So, I really don't much care about codenames unless there's a serious intention to use them during the build of a new version. This was the approach taken by Microsoft: e.g. Chicago became Win95, Memphis became Win98. Of course, a codename is only a work-in-progress name that's "fun" or an in-joke for those who are working on the project. Outside the team, the product-name and version number is all that anyone really cares about.

(off-topic) I see there's a new release of J! (J! 3.8.8). Looks like I have a bit of testing work ahead of me ...

[RussW]

I've added a constant _RES_NAME and temporarily named it "Emu Creek" as that's my last destination and we haven't got a scheme nailed down yet.

Name Suggestions for the first release welcome...

[mandville]

if you picking animal named towns, i always liked (across the water from you ) Waikikamukau

[RussW]

@mandville ... "Waikikamukau" it is then....