Do you plan on making releases?

[rodrigoaguilera]

What stability do you consider for the library? beta? alpha? stable?

[ramonv]

Although the codebase feels a bit odd/ outdated. We are using it in production for about 6 months (>500 transactions per day) and did not see any issues.

[Pelleplutt]

@rodrigoaguilera We have no plans on making any releases. Anything we do push into master should at all times be production worthy.

[Pelleplutt]

@ramonv Please feel free to elaborate on what you mean by "odd/outdated".

[alexisbmills]

+1 for making releases, adopting semantic versioning (https://datasift.github.io/gitflow/Versioning.html)

This ensures anyone utilising the library is aware of new features and can avoid any breaking changes. This is obviously very desirable.

[forceedge01]

+1 to releases. I am looking to use trusttly but this is quite a risk without a tagged version. It would be a super mega good idea if you could tag the latest master branch and push the tag in. That would ensure that when this codebase is fetched by composer it always fetches the tagged version. If you make any changes later on, that just won't automatically come in, but will be an informed change.

[forceedge01]

And by outdated, for me it means that the codebase doesn't use the latest features made available by the language, especially the examples provided. Composer autoloading isn't psr either, it may be put off some devs and force them to develop their own version/fork. Also, is this project compatible with PHP 7? If so you may want to update the dox/composer.json.