readme: document api support level #206
Conversation
|
|
||
| When breaking changes to the Loop client daemon API are made, old fields will be | ||
| marked as deprecated. Deprecated fields will remain supported until the next | ||
| minor release. |
There was a problem hiding this comment.
This is only the case as long as we are in the semver special case of major version 0. Afterwards breaking changes should only happen in major releases. Not sure if we should clarify this or if it's obvious to those who care.
There was a problem hiding this comment.
Yes, I think we can change it if that happens. I am wondering why we don't just release major versions? There will always be improvements. @alexbosworth do you have an opinion on this?
There was a problem hiding this comment.
I don't think we should do a major version as long as we have the -beta suffix. And as long as lnd (and LN in general) is considered beta (#reckless), we probably shouldn't give users the wrong sense of security by removing the -beta suffix in loop.
So probably no major releases for a few more years, IMO.
No description provided.