<p dir="auto">I just updated my composer deps regarding the fresh new Symfony 3.0.4.</p>
<p dir="auto">I was surprised to see when I loaded my application in the Web debug bar the symfony version to 3.0.4-dev.</p>
<p dir="auto">I looked at <a href="https://github.com/symfony/symfony/tree/v3.0.4">v3.0.4 tag</a> and seems that it's not pointing to the good commit.</p>
<p dir="auto">What happened?</p>
<p dir="auto">follow up to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="47624389" data-permission-text="Title is private" data-url="https://github.com/symfony/symfony/issues/12401" data-hovercard-type="issue" data-hovercard-url="/symfony/symfony/issues/12401/hovercard" href="https://github.com/symfony/symfony/issues/12401">#12401</a></p>
<p dir="auto">in the CMF project we have encountered some bugs with 5.3 that we cannot work around (mostly with image manipulation). Also 5.3 can cause issues with memory consumption with composer.</p>
<p dir="auto">Also as long as Symfony core supports 5.3, we kind of also imply we expect the same from our eco system. If however our ecosystem starts using 5.4+ more, then it will become more confusing for our users. Especially hosters (even internal IT) might claim that "5.3 is good enough because its supported by Symfony core" .. so I think its worth thinking about moving to 5.4+, even if there are no specific features we intend to use from 5.4 (we can of course provide traits without moving to 5.4)</p>