Relation to develop branch of "avalanche123/Imagine"

[ejsidisi]

Hi,

With this change last changes in "avalanche123/Imagine" will be available by "php composer.phar update".

This is in relation with issue php-imagine/Imagine#209.

Regards!

[ejsidisi]

Hi @avalanche123,

Sorry for disturbing but this change actually I need in "master" branch because https://github.com/symfony/symfony-standard/blob/v2.2.1/composer.json for "minimum-stability" has "alpha".
Because of that composer will take "dev-master" package instead of "dev-develop" on "https://packagist.org/packages/avalanche123/imagine-bundle" even under requirements I have added "avalanche123/imagine-bundle": "dev-develop".

To add this change in "master" branch do I need to create new PR on it, or I need to wait merging of "dev-develop" with "dev-master"?

Regards!

[ejsidisi]

Hi @avalanche123,

now when I've removed "minimum-stability": "alpha" from https://github.com/symfony/symfony-standard/blob/v2.2.1/composer.json I've got message:

• Installation request for avalanche123/imagine-bundle dev-develop -> satisfiable by avalanche123/imagine-bundle dev-develop.
• avalanche123/imagine-bundle dev-develop requires imagine/imagine dev-master -> no matching package found.

Does anyone knows why? As I can see here https://packagist.org/packages/imagine/imagine "dev-master" package exist.

Is it better to put "imagine/Imagine": "dev-master" in "development/composer.json", and "imagine/Imagine": "dev-master" in "master/composer.json"? Now is "imagine/Imagine": "dev-master" in "development/composer.json"

Regards!