kriswallsmith/assetic dependency about assetmanager HOT 7 CLOSED

That's actually in the readme. You should define that minimum stability, because this module should be working with all versions of assetic. If somethign went wrong with that, I'm guessing you haven't added that. I'd like to set this up to use dev-master but I can not rely on that. I always want the latest stable tag. Do you perhaps have any arguments as to why I should use master? Not trying to sound condescending, I just don't want to set up a different source with no solid reasoning.

Thank you for reporting this though, I was not aware of the fact that stuff went missing.

from assetmanager.

Do you perhaps have any arguments as to why I should use master?

Sorry for my ignorance but I've always thought master is a stable branch. no?!

from assetmanager.

It should be, yes. But that's why tags were invented, to mark something as actually being stable.

from assetmanager.

@dVaffection master is never stable by default. It is what you'd call "nightly" or "bleeding edge"

from assetmanager.

@Ocramius Ok then why Zend Framework suggests to refer to master?

from assetmanager.

@dVaffection suggests does not have a version according to composer's schema definition. It just suggest available packages.

If you are referring to the fact that dev-master got downloaded automatically, that's because you probably have "minimum-stability": "dev" in your composer.json. Some packages simply aren't ready yet (or weren't tagged). Can't do much about it except trust the test suites and builds.

from assetmanager.

I'm closing this issue, I think it's been resolved. Again, thank you @dVaffection. I'm glad you report it when something looks off, rather than ignoring it! :)

from assetmanager.