Skip to content
This repository has been archived by the owner on Jul 22, 2022. It is now read-only.

Composer improvements #370

Merged
merged 1 commit into from
May 4, 2016

Conversation

soullivaneuh
Copy link
Member

  • 2.x-dev
  • Use new composer constraints notation
  • Remove minimum stability

* 2.x-dev
* Use new composer constraints notation
* Remove minimum stability
"symfony-cmf/tree-browser-bundle": "~2.0",
"symfony-cmf/resource-rest-bundle": "~1.0"
"php": "^5.5 || ^7.0",
"sonata-project/admin-bundle": "3.x-dev@dev",
Copy link
Contributor

Choose a reason for hiding this comment

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

same question here, why not 3.*?

Copy link
Contributor

Choose a reason for hiding this comment

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

This should at least be ^3.0@dev and not 3.x-dev@dev (which is double btw, 3.x-dev should be enough).

Copy link
Contributor

Choose a reason for hiding this comment

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

3.x-dev@dev looks indeed fishy…

@SonataCI SonataCI removed the wip/poc label May 2, 2016
"doctrine/phpcr-bundle": "~1.1",
"symfony-cmf/tree-browser-bundle": "~2.0",
"symfony-cmf/resource-rest-bundle": "~1.0"
"php": "^5.5 || ^7.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

any reason to use || instead of the quite common |?

Copy link
Member Author

@soullivaneuh soullivaneuh May 3, 2016

Choose a reason for hiding this comment

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

instead of the quite common |?

This is the problem: it shouldn't.

|| is the new standard. See examples on docs: https://getcomposer.org/doc/04-schema.md

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the info, good to know that the single one is actually sort-of deprecated.

@wouterj
Copy link
Contributor

wouterj commented May 3, 2016

LGTM, CMF is blocked by this atm.

This is precisely why small, scoped PRs are better than large ones. If just the 3.0 dep for block bundle was merged, CMF would be able to continue working on the Symfony 3 support PRs. However, with these (quite irrelevant) "improvements", we're stuck in a discussion and the dep fix doesn't get merged quickly.

@soullivaneuh
Copy link
Member Author

@wouterj Just two points:

  • The working branch of this PR is an unstable one. I can understand your project is stuck but an unstable branch should be used for production or stable dependent releases.
  • The goal of "improving composer" is part of beginning new sonata version management with a good start. It's maybe more painful but necessary IMHO.

@wouterj
Copy link
Contributor

wouterj commented May 4, 2016

see #371

@wouterj wouterj mentioned this pull request May 4, 2016
@greg0ire greg0ire merged commit a88a085 into sonata-project:master May 4, 2016
@soullivaneuh soullivaneuh deleted the composer-improve branch May 4, 2016 10:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants