Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to Stash 0.11 needed #38

Closed
andrerom opened this issue Jan 8, 2014 · 5 comments
Closed

Update to Stash 0.11 needed #38

andrerom opened this issue Jan 8, 2014 · 5 comments

Comments

@andrerom
Copy link
Contributor

andrerom commented Jan 8, 2014

As 0.10 is no longer supported, update to use 0.11 is needed to get the latests, Redis, windows, hhvm fixes and more:
tedious/Stash@v0.10.5...v0.11.4

@lolautruche
Copy link
Contributor

Changing requirement in composer.json from 0.10.* to ~0.10 should be sufficient I think (with a new release of the bundle of course 😉)

@tedivm
Copy link
Member

tedivm commented Jan 8, 2014

Running a few tests now and then I'll take care of this. As a note though the HHVM stuff is not quite ready, we're still working through some issues with phpunit where it's failing on HHVM (specifically it can't create mock drivers), so that bit isn't going to be official until those issues are resolved.

@tedivm
Copy link
Member

tedivm commented Jan 8, 2014

@lolautruche I explicitly don't use the ~ operator with composer for any projects that haven't had their 1.0 release. Until Stash reaches 1.0 the API is not considered final, although I do everything I can to prevent backwards compatibility breaks.

In other words, if a version is X.Y.Z, then right now X is locked at 0 until we're stable, increments in Y represent backwards compatibility breaks, and Z represents functionality changes that you can adopt without issue.

So 0.11.* is really what you should use, and you should only update from 0.10.* if you've looked at the differences and have updated your code. In this case the major difference was that we added the new interfaces in (which should not be a BC break), and have renamed the "extendCache" to just "extend" and given it a new argument.

As a final note, once PSR-6 actually gets passed Stash will start the final steps towards a 1.0 release.

@tedivm
Copy link
Member

tedivm commented Jan 8, 2014

Update published, thanks guys!

@tedivm tedivm closed this as completed Jan 8, 2014
@lolautruche
Copy link
Contributor

OK, thanks for your explanations 😃 .

nicholasruunu pushed a commit to rdey/TedivmStashBundle that referenced this issue Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants