Skip to content
This repository has been archived by the owner on Mar 11, 2022. It is now read-only.

Continued Support Post-Deprecation: Introducing Swift-Cloudant-LTS #194

Closed
DanBurkhardt opened this issue Oct 25, 2021 · 0 comments · Fixed by #195
Closed

Continued Support Post-Deprecation: Introducing Swift-Cloudant-LTS #194

DanBurkhardt opened this issue Oct 25, 2021 · 0 comments · Fixed by #195

Comments

@DanBurkhardt
Copy link

DanBurkhardt commented Oct 25, 2021

Hi friends,

I think this is a perfectly fine library and it is still entirely compatible with Cloudant (Couch DB) Instances hosted in IBM Cloud and elsewhere (Apache Couch DB). Perhaps it doesn't have some new APIs, but in any case, it's a lot of good work and I don't agree with throwing it in the trash.

Therefore we I will be maintaining it here-> https://github.com/GigabiteLabs/swift-cloudant-lts

Some new features included in our latest release but not within the source repository:

  • Support for Couch DB instances hosted on a sub directory (example.com/couch vs couch.example.com)
  • Some additional debug logs

The latest release passes 100% in testing when targeting an IBM Cloud hosted Couch DB instance (at time of release).

Since this library deprecates on Dec 31 2021, please open new issues or move existing ones to our fork.

To the maintainers: much appreciated for all of your work thus far, if you want to add that link above to the Readme, that would be much appreciated & kind to our fellow developers.

Thanks,
Dan

@DanBurkhardt DanBurkhardt changed the title Continued Support Post Deprecation Continued Support Post Deprecation: Introducing Swift-Cloudant-LTS Oct 26, 2021
@DanBurkhardt DanBurkhardt changed the title Continued Support Post Deprecation: Introducing Swift-Cloudant-LTS Continued Support Post-Deprecation: Introducing Swift-Cloudant-LTS Oct 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant