Skip to content
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

Update copyright year range to 2019-2025 #4060

Closed
bschmalhofer opened this issue Jan 14, 2025 · 3 comments
Closed

Update copyright year range to 2019-2025 #4060

bschmalhofer opened this issue Jan 14, 2025 · 3 comments
Assignees
Labels
tidying Tidying of the code
Milestone

Comments

@bschmalhofer
Copy link
Contributor

bschmalhofer commented Jan 14, 2025

It is a new year again. Time to update the copyright year range in the branches rel-10_0, rel-10_1, rel-11_0, and rel-11_1. See also #2077, #740 and #2824 .

Before starting, make sure that the changes from the lower version are already merged into the next higher version.

The first step is to run in the rel-10_0 branch:

git switch rel-10_0
git pull
../CodePolicy_10_0/bin/otobo.CodePolicy.pl --plugins +TidyAll::Plugin::OTOBO::Legal::ReplaceCopyright -a > codepolicy_1.out
Commit only the changed files with git add -u . ; git commit --no-verify as there might be other tidyings and violations.

Then there are some other files that must be adapted manually:

Kernel/System/MigrateFromOTRS/Base.pm
Kernel/Output/HTML/Templates/Standard/CustomerFooter.tt
scripts/test/sample/Loader/CombinedJavaScript.min.js (since rel-11-0)

The merge the changes into rel-10_1 and repeat these steps. Same for rel-11_0 and rel-11_1.

@bschmalhofer bschmalhofer added the tidying Tidying of the code label Jan 14, 2025
@bschmalhofer bschmalhofer added this to the OTOBO 10.0.23 milestone Jan 14, 2025
@bschmalhofer bschmalhofer self-assigned this Jan 14, 2025
bschmalhofer added a commit that referenced this issue Jan 14, 2025
Using TidyAll::Plugin::OTOBO::Legal::ReplaceCopyright from the CodePolicy
bschmalhofer added a commit that referenced this issue Jan 14, 2025
@bschmalhofer
Copy link
Contributor Author

This copyright years have been updated. Tentatively closing this issue.

bschmalhofer added a commit that referenced this issue Jan 14, 2025
Most cases were that no whitspace is recommended after the '<<'
that indicates a here-doc
bschmalhofer added a commit that referenced this issue Jan 14, 2025
Most cases were that no whitspace is recommended after the '<<'
that indicates a here-doc
bschmalhofer added a commit that referenced this issue Jan 15, 2025
Use the testing function TextEqOrDiff() for checking long multiline strings.
@bschmalhofer
Copy link
Contributor Author

Reopening as some tests in rel-11_0 are failing.

@bschmalhofer bschmalhofer reopened this Jan 15, 2025
bschmalhofer added a commit that referenced this issue Jan 15, 2025
Use the testing function TextEqOrDiff() for checking long multiline strings.
@bschmalhofer
Copy link
Contributor Author

Closing again, as tests seem to be passing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tidying Tidying of the code
Projects
None yet
Development

No branches or pull requests

1 participant