Breaking Changes in Lemmy 1.0
Breaking Changes in Lemmy 1.0
38 comments
-
Excited to see the idempotency feature. That will help a lot with double posts from using https://github.com/RikudouSage/LemmySchedule
-
Idk if it will be useful to more active people like you because you will be able to schedule only up to 10 posts at once: https://github.com/N4Y-docker/lemmy-nightly/commit/9eee61dd06220176fbb97ccbba4a594ea21bb5c6
-
-
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
-
I can say I was there when Lemmy 1.0 released!
-
A lot of these should not be called breaking changes. A new API is not a breaking change if the old API remains.
-
Yeah but those changes break clients as soon as they turn down the old API.
-
Indeed, dropping the old API would be the breaking change.
Rich Hickey did a fantastic talk on versioning, breaking changes, and dependencies.
-
-
if
-
-
Does this mean Lemmy 0.20 is now 1.0? What prompted the change?
-
And here I was thinking it would go all the way to 0.99 before getting to 1.0...
-
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 av.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.
-
On the other hand it gives an indication to client developers that such big breaking changes wont be a regular occurence. So they have a reason to upgrade and then keep using 1.0 long-term. I believe that practically all the needed breaking changes are already implemented, and remaining issues are mostly new feature requests which can be added as new api endpoints or parameters.
-
-
Maturity I think. New Lemmy is good enough to make the change.
-
-
Holy shit, it's going gold!
-
This is epic. I really hope Laurence can find some time to make Sync for Lemmy support it.
-
Will the new lemmy ui be ready for 1.0?
-
Yes we always release backend and frontend versions together.
-
Can't give an ETA yet. I've got a few more back-end things to finish up, then @sleeplessone1917 and I will work on lemmy-ui.
Then I also gotta work on getting jerboa updated also. So much work and so few developers.
-
-
Really looking forward to SSO support!
-
Oh yes!
-
Nice
-
Does this mean you renamed just the DB columns, but not the API keys?
-
They're all renamed, that PR just hasn't been deployed to voyager.lemmy.ml yet.
-
-
Quick question mostly for @phiresky:
Are you targeting post tags for 1.0 or for later?Thx for the work.
-
wow! Huge, just when I am back to the saddle
-
CORS is broken on voyager.lemmy.ml. Can you please fix it?
-
💪
38 comments