-
Notifications
You must be signed in to change notification settings - Fork 163
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
Let's update Copyright notice to 2019 #985
Comments
@llorllale/z please, pay attention to this issue |
@yegor256 should we maintain a range of dates for the copyright notice? As far as I am aware, the really important date is the one when the work was published (the start date). You may add a "revised date" to the notice if a file's contents changes "significantly", but do we really need to? Guava certainly doesn't do it. I'm guessing the hassle isn't worth it. Sources: |
@yegor256 ping |
@llorllale let's do a years range, this is what we do in all other projects |
@0crat in |
@llorllale Job #985 is now in scope, role is |
Bug was reported, see §29: +15 point(s) just awarded to @fabriciofx/z |
…verification is not working
@llorllale I found out that dates already changed by @yegor256 in 100885a. But dates verification is not working and I add a new TODO. |
…s verification is not working
…s verification is not working
@0crat continue |
@llorllale I assume that we can close this. |
@aivinog1 ask the ticket's reporter |
@llorllale Thanks. @fabriciofx Can you close this ticket? |
@llorllale I remind you about #1148. Can you fix my reputation? |
@llorllale I'll close this issue now. @aivinog1 good work! Congratulations! |
@sereshqua/z please review this job completed by @aivinog1/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed |
The job #985 is now out of scope |
…s verification is not working
@sereshqua done, thanks. |
@0crat quality acceptable |
Quality review completed: +4 point(s) just awarded to @sereshqua/z |
Let's update Copyright notice to 2019.
The text was updated successfully, but these errors were encountered: