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

ETA for DBAL 2.6 #2712

Closed
stof opened this issue May 5, 2017 · 11 comments
Closed

ETA for DBAL 2.6 #2712

stof opened this issue May 5, 2017 · 11 comments

Comments

@stof
Copy link
Member

stof commented May 5, 2017

The master branch of DBAL contains a bunch of unreleased features, including the new JsonType merged nearly 1 year ago.
What is the ETA for release DBAL 2.6.0 ?

@Ocramius
Copy link
Member

Ocramius commented May 5, 2017

I think it's mostly https://github.com/doctrine/dbal/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.6

Important bits are MySQL 5.7 support (because MySQL has awesome BC policies, sigh), which wasn't yet evaluated, and things that are marked as "feature/improvement". Fixes can be applied also later, but I think these will be the last "features" for the 2.x branch.

@deeky666
Copy link
Member

deeky666 commented May 5, 2017

👍 I will try to work through these open issues in the next few days if I find time.

@Tobion
Copy link
Contributor

Tobion commented May 12, 2017

I'd say it's important to reconsider the JSON type naming before releasing 2.6. See #2723

@RinkAttendant6
Copy link

2.6 doesn't seem to be backwards-compatible with 2.5 considering that the minimum requirement is PHP 7 so perhaps a major release (3.0.0) is more appropriate according to semver?

Is there going to be a migration guide for 2.5.x to the new release, or are the changes not significant enough for that to be considered?

I am in the middle of migrating an application from PHP 5.3 to PHP 7.0 so compatibility will be a very useful thing to know.

@Ocramius
Copy link
Member

2.6 doesn't seem to be backwards-compatible with 2.5 considering that the minimum requirement is PHP 7 so perhaps a major release (3.0.0) is more appropriate according to semver?

@RinkAttendant6 bumping dependency requirements does not count as a BC break, and that is even specified in semver (semver/semver#148)

Is there going to be a migration guide for 2.5.x to the new release, or are the changes not significant enough for that to be considered?

See UPGRADE.md

I am in the middle of migrating an application from PHP 5.3 to PHP 7.0 so compatibility will be a very useful thing to know.

You'll need 7.1 ;-)

@RinkAttendant6
Copy link

You'll need 7.1 ;-)

According to https://github.com/doctrine/dbal/blob/master/composer.json#L15, it still says 7.0 but I assume this will be bumped to 7.1 upon release?

In that case I guess I'll have to stick with 2.5.x, can you tell me if there's any issues with using 2.5.x on PHP 7.0?

@Ocramius
Copy link
Member

Ocramius commented May 22, 2017 via email

@schodemeiss
Copy link

Any idea how far away we are from a 2.6? I'm in need of some of the goodness merged in a while back?

@Tobion
Copy link
Contributor

Tobion commented Jul 24, 2017

DBAL 2.6 is released so this issue can be closed. @Ocramius please merge doctrine/orm#6580 and make a patch release so we can actually use DBAL 2.6

@Ocramius
Copy link
Member

Release of ORM 2.6 is probably happening next week anyway.

@github-actions
Copy link

github-actions bot commented Aug 4, 2022

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants