Please start using tags about silverstripe-widgets HOT 7 CLOSED

At the moment we're looking at semantic versioning in core, after which I'm sure we'll start to look again at how we go about versioning all our other modules. :)

from silverstripe-widgets.

I've pushed a 0.2.0 tag as the first start. Once guidelines are introduced then we'll take them on from there.

from silverstripe-widgets.

@g4b0 Off-topic, I found out something recently (you might already know about this) that I now use to ensure I get predictable versions of modules that aren’t tagged - you can point to a specific commit, e.g.:

'silverstripe/widgets': 'dev-master#8ee406675e'

All SilverStripe modules should be tagged of course, but I’ve found it useful for other module authors :)

from silverstripe-widgets.

Good news for me @kinglozzer, I did not know this feature!

from silverstripe-widgets.

Hey @kinglozzer which code are you using after dev-master# ? git log show longer hashes than yours..

from silverstripe-widgets.

You can use the full commit hash or the short one, both should work :)

On Friday, 31 October 2014, Gabriele Brosulo [email protected]
wrote:

Hey @kinglozzer https://github.com/kinglozzer which code are you using
after dev-master# ? git log show longer hashes than yours..

—
Reply to this email directly or view it on GitHub
#79 (comment)
.

from silverstripe-widgets.

Ok, thanks. Maybe module versioning needs a documentation page?

from silverstripe-widgets.