Zoho SDK versioning and repositories need permanent naming/versioning changes moving forward
I spent all day on this, a simple problem. Add a note to a lead, retrieve the notes from the lead.
Finding samples and documentation is VERY difficult BECAUSE the versioning is totally non-standard. The php SDK doesn't follow SemVer. I suppose it may inside every NEW repository, but that isn't useful.
SemVer, changelogs, and general open source versioning practices exist for a reason. Why did Zoho decide to defy general best practices?
This shouldn't be the picture of an update:
SemVer, changelogs, and general open source versioning practices exist for a reason. Why did Zoho decide to defy general best practices?
This shouldn't be the picture of an update:
An upgrade of the PHP SDK 4.0.0 -> 2.0.0?? That makes no sense.
What do you think a search for issues, samples or documentation looks like when a developer encounters an issue? There are *multiple* 2.0.0 versions of the SDK. Again, how does that make sense?
Strong suggestion:
What do you think a search for issues, samples or documentation looks like when a developer encounters an issue? There are *multiple* 2.0.0 versions of the SDK. Again, how does that make sense?
Strong suggestion:
- change the latest repo to `zohocrm/php-sdk` (no version!)
- find the highest major version of any versioned version of the zohocrm/php-sdk, increment it by one and start using that e.g. 10.0.0
- start using branches and tags