Time for a new tag

[guywithnose]

Updating the composer json to include zetacomponents/base is pretty important. Could we get an updated tag with this change.

[derickr]

What do I need to do to make this work?

http://derickrethans.nl | http://xdebug.org
twitter: @derickr and @xdebug

[guywithnose]

There is a commit in the master branch that has not been tagged. Could you create a new tag with a new version on the current master branch and update packagist? Right now we have to either point our composer file to dev-master or manually include "zetacomponents/base": "*".

[guywithnose]

This can easily be done through github's release tool

[andrerom]

A 1.5beta1 tag would be good, it would speed up composer use a lot if Zeta Components get new relevant tags, even if just beta tags.

But I think @guywithnose hints that Base should be updated also as there is probably dependencies.
Two options there:

• Tag new stable release of Base, no further changes needed, composer picks latests stable by default.
• Tag new beta release of Base and update all Components to require this version in the stability you set, example; Base tag: 1.9beta1, composer.json file of all other components that depends on Base: "zetacomponents/base": "~1.9@beta", this will allow them to also pull in Base 1.x versions of minimum beta stability as of version 1.9.