8000 Add "dev" keyword to symfony/symfony package by nicolas-grekas · Pull Request #51811 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

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

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

nicolas-grekas
Copy link
Member
Q A
Branch? 6.4
Bug fix? no
New feature? no
Deprecations? no
Tickets -
License MIT

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?

image

@carsonbot carsonbot added this to the 6.4 milestone Oct 2, 2023
@fabpot
Copy link
Member
fabpot commented Oct 2, 2023

That's brilliant!

@stof
Copy link
Member
stof commented Oct 2, 2023

@nicolas-grekas can you do the same for the polyfill mono-repo then ?

@nicolas-grekas
Copy link
Member Author

On it. Meanwhile I updated the PR for the contracts.

@ro0NL
Copy link
Contributor
ro0NL commented Oct 2, 2023

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

@wouterj
Copy link
Member
wouterj commented Oct 2, 2023

In short:

  • We can't remove the package, it will break applications on <3.4 beyond fixable
  • We can't keep the package, but no longer propagate new tags to Packagist
  • There is a big "marketing value" in making releases on the mono repo
  • Marking Symfony as abandoned gives the wrong signal, unless you are well into the community and are aware of the Flex initiative

@ro0NL
Copy link
Contributor
ro0NL commented Oct 2, 2023

i was thinking "abandoned": "Use individual symfony/* packages instead"

then yes, signaling something to all existing installations could create some drama and/or unnessecary work. Perhaps it's not worth it.

@fabpot
Copy link
Member
fabpot commented Oct 2, 2023

Thank you @nicolas-grekas.

@fabpot fabpot merged commit 8d8acf1 into symfony:6.4 Oct 2, 2023
fabpot added a commit to symfony/ux that referenced this pull request Oct 2, 2023
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
fabpot added a commit to symfony/polyfill that referenced this pull request Oct 2, 2023
…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
@nicolas-grekas nicolas-grekas deleted the sf-dev branch October 16, 2023 20:21
This was referenced Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants
0