Merge ~ines-almeida/launchpad:update-copyright-date-across-launchpad into launchpad:master
Proposed by
Ines Almeida
Status: | Merged |
---|---|
Approved by: | Ines Almeida |
Approved revision: | e882cc9b90a0c7771bc8f0057a23c7ab1cd4937b |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~ines-almeida/launchpad:update-copyright-date-across-launchpad |
Merge into: | launchpad:master |
Diff against target: |
210 lines (+17/-17) 16 files modified
LICENSE (+1/-1) doc/conf.py (+1/-1) lib/lp/app/stories/basics/copyright.rst (+2/-2) lib/lp/app/templates/base-layout-macros.pt (+1/-1) lib/lp/app/tour/api (+1/-1) lib/lp/app/tour/branch-hosting-tracking (+1/-1) lib/lp/app/tour/bugs (+1/-1) lib/lp/app/tour/community (+1/-1) lib/lp/app/tour/community-support (+1/-1) lib/lp/app/tour/feature-tracking (+1/-1) lib/lp/app/tour/index (+1/-1) lib/lp/app/tour/join-launchpad (+1/-1) lib/lp/app/tour/ppa (+1/-1) lib/lp/app/tour/release-management (+1/-1) lib/lp/app/tour/translation (+1/-1) lib/lp/services/librarianserver/web.py (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jürgen Gmach | Approve | ||
Review via email: mp+460944@code.launchpad.net |
This proposal supersedes a proposal from 2024-02-21.
Commit message
Remove date range from copyright note in user-facing places
This is no longer necessary and only creates extra work once a year. Canonical's legal team agreed with having the start year, but not the range.
Blog post about this topic: https:/
Description of the change
Note that in this MP we are not updating the copyright message in every code file, only the ones more user facing.
Discussion about this topic: https:/
Blog post about this topic: https:/
To post a comment you must log in.
Your commit message tells the what, but not the why. Could you please add a reason why we do this? If you could find a link to the discussion we had would be awesome (to this MP, not to the commit message). I think there were also a couple of blog posts out there discussing why this makes sense.
Uh, that is what I call a massive pull request... /github. com/curl/ curl/pull/ 10205/files
https:/
And the blog post I mentioned was /hynek. me/til/ copyright- years/
https:/
I think it would make sense to add it to the commit message, I am pretty sure Guruprasad mentioned it in the discussion we had back then.