8000 Bump license year to 2023 by fabpot · Pull Request #48845 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

Bump license year to 2023 #48845

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”, 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
Jan 1, 2023
Merged

Bump license year to 2023 #48845

merged 1 commit into from
Jan 1, 2023

Conversation

fabpot
Copy link
Member
@fabpot fabpot commented Jan 1, 2023
Q A
Branch? 5.4
Bug fix? no
New feature? no
Deprecations? no
Tickets n/a
License MIT
Doc PR n/a

@carsonbot carsonbot added this to the 5.4 milestone Jan 1, 2023
@fabpot fabpot merged commit 25d3ecc into symfony:5.4 Jan 1, 2023
@fabpot fabpot deleted the license-year branch January 1, 2023 08:34
@@ -1,4 +1,4 @@
Copyright (c) 2004-2022 Fabien Potencier
Copyright (c) 2004-2023 Fabien Potencier
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copyright (c) 2004-present Fabien Potencier

What about using the "present" variant? This would indicate that the file was created or modified between 2004 and the present time. You would not need to update the copyright notice each year, as it already covers the current year and any future years.

It's also worth noting that the specific format of the copyright notice is not as important as the information it conveys. As long as you include the required information, you have some flexibility in how you present it.

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.

3 participants
0