The names of previous Lemmy versions were all very boring and repetetive. We need something much more creative. Any ideas?

  • xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    48
    arrow-down
    1
    ·
    8 months ago

    Eh, if someone on the team is feeling creative I don’t mind fun version numbers but semantic versioning is quite searchable and reduces confusion.

    • Shatur@lemmy.ml
      cake
      link
      fedilink
      arrow-up
      9
      ·
      8 months ago

      One does not exclude the other. You can have a fancy name and a semantic versioning.

      • Tanoh@lemmy.world
        link
        fedilink
        arrow-up
        17
        ·
        8 months ago

        The problem is that it is almost always just one lf them. Let’s say that v0.20 is called “Fuck Spez” and v0.21 is called “YouKnowWhatFuckMuskToo”.

        Most people are going to refer to them by either the number or the name, almost never are both used. The biggest problem with names is that they are rarely sortable (google did it with android, for a bit but not anymore), so in the future it is hard to know which is which without resorting to looking at a list of releases.

        For example, in the future when we are on v0.30 someone might say “ah, but this has been an issue since “Fuck Spez”.” And then most likely you have to look it up to know what they are talking about. If we coulld force everyone to alwaya write “version “Fuck Spez” (v0.20)” then it would be great, but that never happens.

        I personally prefer just semantic versioning for this reason.

        • TheGalacticVoid@lemm.ee
          link
          fedilink
          arrow-up
          2
          ·
          8 months ago

          People can search the name or SemVer and get the other name. It’s not hard, not time-consuming, and it’s way more fun. I genuinely miss when Android had dessert-themed names because it made the updates that much more exciting

        • Hamartiogonic@sopuli.xyz
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          8 months ago

          What if the names were picked from whatever news was prominent during the release week. During last summer we could have had something like blackout or APIcalypse.

      • xmunk@sh.itjust.works
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        8 months ago

        I think that’s the case and why I said it’s fine in my OC, but the more I think about it I’m slightly concerned it might cause some fragmentation “Does anyone know how to force a user sync in Lightfoot?” and “How can I sync users (forced) in v13.8.12?”

        • kautau@lemmy.world
          link
          fedilink
          arrow-up
          6
          ·
          8 months ago

          Yeah it muddles with searching for answers, especially when the names are common things. Apple can get away with naming macOS on places in California, but it’s going to be tough searching “having trouble posting comments on Thor” or whatever. The naming scheme can work, but it has to be very unique

  • GBU_28@lemm.ee
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    2
    ·
    8 months ago

    It’s software versioning, not a new breakfast cereal

    • livus@kbin.social
      link
      fedilink
      arrow-up
      10
      ·
      8 months ago

      This, it means sooner or later there will be a Lemmy version called Orgasmatron.

  • Dessalines@lemmy.ml
    link
    fedilink
    arrow-up
    14
    ·
    8 months ago

    We’ve been notoriously bad about doing more frequent releases, but if we were to release every month, then naming them could get annoying really quickly.

    I’d prefer to just stay with the semantic version numbering, like a lot of projects with a ton of releases do. Like look at react’s releases.

    The fun named versioning makes sense for operating systems, that release only like once a year, but not for apps, docker services, libraries, etc.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    8 months ago

    No we don’t.

    Versioning like this is good for knowing how far off you are from current.

  • RedWizard [he/him, comrade/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    3
    ·
    8 months ago

    Hmm so you’re looking for a naming theme like the old Android scheme of Desserts or MacOS California Parks.

    List off the top of my head

    • Tree Species
    • Cities, Towns, Villages in Cuba
    • Mushroom Species
    • Names of Wildflowers

    That’s all I got for now.

  • Omega_Haxors@lemmy.ml
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    8 months ago

    Add ridiculous titles for each version. For example. Lemmy Release v0.18.1: The Revengence

    I just think it would be funny to have “Are you still on Revengence? Make sure you update to Snickerdoodle” pop up from time to time.

  • souperk@reddthat.com
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    8 months ago

    It sounds a bit too soon to use release names, especially given that Lemmy is still in alpha.

    When a major release comes out, I suggest using colony names (fictional or real), like the pirate republic.

    In general, I like names that highlight the decentralised aspect of the fediverse.

  • IninewCrow@lemmy.ca
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    2
    ·
    8 months ago

    Books of the Bible, Torah and Koran

    The amount of controversy it would generate would propel Lemmy into international headlines.

  • grant 🍞@toast.ooo
    link
    fedilink
    English
    arrow-up
    6
    ·
    8 months ago

    Having a name for a version would be nice for each major release (1.0.0 would have a name but 1.x.x wouldn’t, but 2.0.0 would, etc)

  • pmk@lemmy.sdf.org
    link
    fedilink
    arrow-up
    6
    ·
    8 months ago

    I like the TeX version scheme, it starts with version 3. After that it’s:
    3.1
    3.14
    3.141
    3.1415 etc. Current stable release is 3.141592653. The message is that each version is a more accurate approximation of pi. It’s not growing much bigger, but better.