2025-02-03 - Breaking Changes in Lemmy 1.0
join-lemmy.org
    • Dessalines@lemmy.mlMEnglish
      1·
      2 months ago

      Lots of things, but mainly that lemmy is pretty stable, and its been a year since the last breaking changes release.

      I was also kind of opposed to a v1.0, and wanted lemmy to be considered alpha/beta level software, because I know when we release a v.1.0, people are going to expect the same enterprise-level and bug-free software from a ~4 person dev team as they do from a multi-million dollar company. Also it gives us less freedom to make breaking changes, which can be restrictive for back-end devs.

      But now we can just adopt proper semver, and the next breaking changes releases can upgrade the MAJOR version.

  • toastal@lemmy.mlEnglish
    1·
    2 months ago

    1.0 would be the perfect time to have the code, bug tracker, etc. migrated off of Microsoft GitHub

      • toastal@lemmy.mlEnglish
        01·
        2 months ago

        Visibility to who? Normies? Search engines favoring corpo slop? You could make a readonly mirror if felt it necessary (it isn’t). If you have a modus operandi for you product or service, you would be better off choosing tools that align with those ideals. This instead says collaborator privacy/freedom is not our priority & we don’t actually follow our values.

        • OsrsNeedsF2P@lemmy.mlEnglish
          1·
          2 months ago

          I ran a large open source project, and when we switched to Gitlab the number of contributors dropped like a rock. Despite linking to our Gitlab repo everywhere, people weren’t finding it on Google or GitHub search, and those who did weren’t interested in creating a second account.

          We went from probably getting a new contributor every month to maybe getting a couple a year. It significantly slowed down progress.

  • db0@lemmy.dbzer0.comEnglish
    1·
    2 months ago

    Oof, lots of work to do for everyone.

    If anyone can figure out all the non-mentioned API changes and write them here it would be useful for people like me to avoid having to reverse engineer things

      • db0@lemmy.dbzer0.comEnglish
        0·
        2 months ago

        Ah, good to know before I start developing. Can you let me know when we can start the development as I don’t want to use the API and then discover it’s missing more PRs?

        • Dessalines@lemmy.mlMEnglish
          0·
          2 months ago

          I can’t say yet, as we’re still adding things. If you’re not using lemmy-js-client, then as long as your types are generated from it’s main branch directly, then you should be fine.

          • db0@lemmy.dbzer0.comEnglish
            0·
            2 months ago

            I’m not using the js-client. I’m updating pythorhead so I need to make sure the API is at the final version before I can match it. And to match it I need the patches to be in so I can read the doc, and/or import the swagger.

            I will do what I can in advance, but to do the pre-development you asked for, we do need the final version up somewhere.