update copyright year

[fabriciofx]

@exper0 what you think? It's good enough to close #523?

[exper0]

@fabriciofx I think it would be more suitable to replace 2015 with 2016. Listing years means that we need to list all of them from the beginning - it wasn't done before so I think it's reasonable to have only one latest year.
Btw, #523 is not classified and not assigned - not sure if this PR will be accepted.

[davvd]

@fabriciofx I will find a reviewer for your pull requests shortly, thanks for contribution!

[davvd]

@mkordas this pull request is for you,please review

[exper0]

@davvd what about underlying issue #523 ? it's not even dispatched.

[mkordas]

@fabriciofx you should ask @yegor256 to assign you to #523

[mkordas]

@fabriciofx we should have 2015-2016 instead of 2015, 2016

[yegor256]

@fabriciofx this is not a good solution, since we will have to do it every year, again and again (spending money for this). Instead, we should make sure the build breaks when the year in the license is wrong. This should happen automatically.

[mkordas]

@yegor256 who will be responsible to fix failed build on 1st Jan 2017?

[mkordas]

@fabriciofx please see how it was done in Qulice: yegor256/qulice#624

[yegor256]

@fabriciofx the author of the first pull request. He/she simply won't be able to merge it, because of the check.

[mkordas]

@yegor256 make sense, thanks

[mkordas]

@fabriciofx do you need help?

[fabriciofx]

@mkordas I did a new patch, and pushed it to my fork, but it failed into travis test (permission denied to execute the ./years.sh script). Could you check it?

[mkordas]

@fabriciofx have you added execute permission?

[fabriciofx]

@mkordas yes. rwxr-xr-x permission here.

[mkordas]

@fabriciofx please follow the same approach as in yegor256/qulice#624, it was working there

[mkordas]

@fabriciofx please see http://stackoverflow.com/questions/9027584/how-to-change-the-file-mode-on-github

[fabriciofx]

@mkordas I fixed it, but the problem now is with esd ruby package: https://travis-ci.org/yegor256/takes/builds/104171779. Should I delete this PR and resend it?

[mkordas]

@fabriciofx you can just trigger build again by pushing new commit or from Travis GUI

[fabriciofx]

@mkordas could you see it now? Passed in all tests!

[davvd]

@ypshenychka please, check this issue for QA compliance, as per par.24

[ypshenychka]

@fabriciofx First of all please make sure that ticket #523 is dispatched and you're assigned as a performer. Oterwise you will be simply not paid for your effort if another person will be assigned to it. .

[ypshenychka]

@fabriciofx Also why have you closed this PR and still continue work on it?

[mkordas]

@ypshenychka why you don't chase @fabriciofx for an answer?

[ypshenychka]

@mkordas I see that there is no resolution by @yegor256 in #523. So I guess all we can do here is to wait until issue is dispatched.

[mkordas]

@ypshenychka thanks, I will be chasing @yegor256

[mkordas]

@yegor256 can you dispatch #523? @ypshenychka is waiting for your decision

[yegor256]

@mkordas I closed #523 and created another one: #627

[yegor256]

@fabriciofx can you fix #627 in this PR?

[mkordas]

@ypshenychka #523 is closed, please decide about quality here

[ypshenychka]

@davvd Quality is bad here since the PR was done without assignment and didn't bring any value for the project.
@mkordas I would advise you to not proceed with code review in such "unauthorized" PR until it is valid.

[ypshenychka]

@davvd Quality is bad.

[ypshenychka]

@davvd @yegor256 Please consider this ticket.