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

year check in LICENSE.txt #627

Closed
yegor256 opened this issue Feb 28, 2016 · 17 comments
Closed

year check in LICENSE.txt #627

yegor256 opened this issue Feb 28, 2016 · 17 comments

Comments

@yegor256
Copy link
Owner

Let's create a check in pom.xml (somehow), that will fail the build if LICENSE.txt doesn't have 2014-2016 text.

@yegor256 yegor256 changed the title year check in LICENSE.tx year check in LICENSE.txt Feb 28, 2016
@davvd
Copy link

davvd commented Feb 28, 2016

@yegor256 I tagged this as "bug"

@davvd
Copy link

davvd commented Feb 28, 2016

@yegor256 attached this issue to milestone "1.0" (let me know if this is wrong)

@davvd davvd added this to the 1.0 milestone Feb 28, 2016
@davvd
Copy link

davvd commented Feb 28, 2016

@yegor256 thanks for tis bug, I topped your account for 15 mins, transaction 000-333acd31

@davvd
Copy link

davvd commented Feb 29, 2016

@raphaelln can you please help? Keep in mind this. If you have any technical questions, don't hesitate to ask right here... The cost of this task is 30 mins (this is exactly how much will be paid, not less not more), when the task is done

raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
raphaelln pushed a commit to raphaelln/takes that referenced this issue Mar 1, 2016
@rultor rultor closed this as completed in abdd7c0 Mar 9, 2016
@raphaelln
Copy link
Contributor

@davvd the issue was closed, could you proceed please.
thanks.

@davvd
Copy link

davvd commented Mar 10, 2016

@rultor rultor closed it (automatically), @yegor256 please take a look

@davvd davvd reopened this Mar 10, 2016
@rultor
Copy link
Collaborator

rultor commented Mar 10, 2016

@rultor rultor closed it (automatically), @yegor256 please take a look

@davvd I'm sorry, I don't understand you :( Check this page and try again please

@davvd
Copy link

davvd commented Mar 10, 2016

@davvd the issue was closed, could you proceed please.
thanks.

@raphaelln no problem :)

@yegor256
Copy link
Owner Author

@raphaelln please post a link to the pull request, where it was fixed

@raphaelln
Copy link
Contributor

@yegor256 sure, following the PR #633 for this issue.

@yegor256
Copy link
Owner Author

@raphaelln thanks

@davvd
Copy link

davvd commented Mar 15, 2016

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

@ypshenychka
Copy link

@davvd Quality is good.

@davvd
Copy link

davvd commented Mar 15, 2016

@davvd Quality is good.

@ypshenychka thanks a lot :)

@raphaelln
Copy link
Contributor

@davvd everything is ok here could you please proceed.

@davvd
Copy link

davvd commented Mar 21, 2016

@davvd everything is ok here could you please proceed.

@raphaelln OK

@davvd
Copy link

davvd commented Mar 22, 2016

@raphaelln I added 10 mins to @ypshenychka (for QA review) in transaction 81197360; thanks, I just added 30 mins to your account, payment AP-22D74699JV219591B, 254 hours and 34 mins spent; +30 to your rating, your total score is +90

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants