-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Add "dev" keyword to symfony/symfony package #51811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub& 8000 rdquo;, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
That's brilliant! |
@nicolas-grekas can you do the same for the polyfill mono-repo then ? |
On it. Meanwhile I updated the PR for the contracts. |
i appreciate the effort to keep symfony/symfony available as a package, but what for exactly? i assumed git clone+link would be the better practice for dev |
In short:
|
i was thinking then yes, signaling something to all existing installations could create some drama and/or unnessecary work. Perhaps it's not worth it. |
Thank you @nicolas-grekas. |
This PR was merged into the 2.x branch. Discussion ---------- Add "dev" keyword to symfony/ux package | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | Tickets | - | License | MIT Same as symfony/symfony#51811 Even if symfony/ux is not registered on packagist, I'm doing this for completeness and consistency among all our meta-repositories. Commits ------- c42a666 Add "dev" keyword to symfony/ux package
…kas) This PR was merged into the 1.x branch. Discussion ---------- Add "dev" keyword to symfony/polyfill package See symfony/symfony#51811 Commits ------- 0bc9478 Add "dev" keyword to symfony/polyfill package
We're periodically wondering about how we should tell people that they should require individual symfony packages instead of the meta repo. Marking the symfony/symfony package as "abandonned" on packagist is very close on a technical level, but semantically it's inaccurate.
I thought we might want to declare symfony/symfony as "for dev". WDYT?