Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Aug 23, 2023. It is now read-only.

Conversation

@jwage
Copy link
Member

@jwage jwage commented Jun 15, 2018

No description provided.

@jwage jwage added this to the 1.0.1 milestone Jun 15, 2018
@jwage jwage self-assigned this Jun 15, 2018
@jwage jwage requested a review from Majkl578 June 15, 2018 15:57
@Majkl578
Copy link
Contributor

Nice dependency hell here. 😃 Reverse dependency doesn't allow @dev dependency so it fails to install.

@Majkl578
Copy link
Contributor

cc @Ocramius? Tag this as 1.0.1 (then it should build on CI), then bump Common to require ^1.0.1?

@jwage
Copy link
Member Author

jwage commented Jun 15, 2018

I think that makes sense to me.

  1. Release this as 1.0.1
  2. Update doctrine/common 2.9@dev to require 1.0.1
  3. Release doctrine/common 2.9.0 stable.
  4. Update doctrine/reflection to point to 2.9.0 stable and release as 1.0.2
  5. Update doctrine/common to point at doctrine/reflection 1.0.2 and release it as 2.9.1

I think that is right :)

@Majkl578
Copy link
Contributor

We don't really need 1.0.2 tagged or bumped again in Common, just remove @dev from require-dev dependency in master after Common 2.9.0 is shipped.

Let's wait for @Ocramius.

@jwage
Copy link
Member Author

jwage commented Jun 15, 2018

Sounds good.

"phpunit/phpunit": "^7.0",
"doctrine/coding-standard": "^4.0",
"doctrine/common": "^2.8",
"doctrine/common": "^2.9@dev",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Urgh, this is still required? (I missed that before)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Ocramius yes, because of this https://github.com/doctrine/reflection/blob/master/lib/Doctrine/Common/Reflection/RuntimePublicReflectionProperty.php#L25

Which is not a standalone project. We could possibly remove the tests that verify that functionality and we could temporarily remove the doctrine/common dependency for the tests. Then reintroduce the tests once doctrine/common 2.9 stable is released. It just buys is a few less steps I think.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also OK to have a release with a failure as long as we know what we are doing

@alcaeus alcaeus removed this from the 1.0.1 milestone Dec 2, 2019
@alcaeus
Copy link
Member

alcaeus commented Dec 2, 2019

@jwage 1.0.1 is not going to happen. We're at doctrine/common 2.11 in the meantime, so is this still necessary, and if so, what changes should we make before tagging 1.1.0?

@alcaeus
Copy link
Member

alcaeus commented Dec 3, 2019

Fixing in #25.

@alcaeus alcaeus closed this Dec 3, 2019
@alcaeus alcaeus deleted the doctrine-common-dep branch December 3, 2019 15:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants