-
Notifications
You must be signed in to change notification settings - Fork 85
No versions available #39
Comments
I have created tags for you previous versions, while this isn't too useful for people going forward it would be nice if you retain them: https://github.com/elliotchance/xero-api/releases eg: git tag v0.5 0270057
git tag v0.4 0f1aac2
...
git push origin v0.5 v0.4 ... |
👍, would really like to have version tags. |
Another developer got so fed up with this library that he started a replacement from scratch: https://github.com/calcinai/xero-php The code is MUCH better and he is very responsive to bug reports and pull requests. I suggest everybody start putting their effort in over there instead. |
There hasn't been an commit since then but happy to add in versioning next time. @gerrywastaken - yes it seems to be a great project, we are very supportive. If you don't have anything constructive to contribute in here though, maybe you should focus your time on being constructive there? |
@ronanq you responded to my unconstructive comment in less than an hour! For two months @elliotchance and @Cbakker have waited for a response to their constructive suggestions of adding tags. I won't apologize for pointing out that Xero is actively ignoring developers, although I don't blame you for this as it seems to be a company wide issue (see: http://xero.uservoice.com/forums/5528-xero-core-api) Anyway, glad to hear you will be adding the tags. |
The package has to be registered on packagist for people to use it. This is very easy, just goto packagist.org and slick the Submit a Package button.It is bad practice for people to run off your
master
branch since that could change and isn't guaranteed to be stable. When you add git tags likev1.0
it will be recognised as a release by both composer and Github. For each release in the future just add another tag thats appropriate for the version.The text was updated successfully, but these errors were encountered: