Skip to main content


Lemmy Release v0.19.15 and Testing for 1.0


in reply to Nutomic

Is there a reason why you gathered so many features in a single update? It seems to be challenging to test all these features at once, why not just publish them step by step in smaller updates? For instance, Mastodon have even split quote posts into two separate versions (first backend, then frontend) to make this process smoother.
in reply to vermaterc

It mainly has to do with trying to keep breaking changes releases as infrequent as possible. These make things difficult for app developers trying to keep up.
in reply to Dessalines

Not sure that is the correct approach. break frequently break often seems better (that's what PHP and java seem to do as far as i can tell, unlike python 3 which caused a lot of drama).

notify a API is deprecated. give some time for users to update to the new API (1 year?) and then remove it.

Of course after version 1.0 there might be less breakage so it won't be a be problem.

in reply to wiki_me

Breaking frequently is fine for libraries where all versions are available and usable.

It's not good for API's, where every single change isn't backwards compatible and available. We have lemmy apps that still aren't supporting API changes added over a year ago. We even had one such case last week.

in reply to Dessalines

We have lemmy apps that still aren’t supporting API changes added over a year ago. We even had one such case last week.


That sounds like something could be improve. is there some sort of warning mechanism in place?

Say when using a lemmy client. the client either specifies its a production build. or if its not then the lemmy server reports where deprecated API's are used.

in reply to wiki_me

Its just devs that aren't watching the releases, and using custom javascript libraries rather than the ones we publish.