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

For #968. Removing Guava's code. #979

Closed
wants to merge 4 commits into from
Closed

For #968. Removing Guava's code. #979

wants to merge 4 commits into from

Conversation

zCRUSADERz
Copy link
Contributor

For #968

  • Updated cactoos-matchers to 0.15
  • Replaced Guava's code on cactoos
  • Replaced statis matchers on cactoos-matchers
  • Updated puzzle

@0crat 0crat added the scope label May 23, 2019
@0crat
Copy link
Collaborator

0crat commented May 23, 2019

Job #979 is now in scope, role is REV

@0crat
Copy link
Collaborator

0crat commented May 23, 2019

This pull request #979 is assigned to @Serranya/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @paulodamaso/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be no monetary reward for this job

@zCRUSADERz zCRUSADERz closed this May 23, 2019
@0crat
Copy link
Collaborator

0crat commented May 23, 2019

Job was finished in 10 hours, bonus for fast delivery is possible (see §36)

@0crat
Copy link
Collaborator

0crat commented May 23, 2019

@sereshqua/z please review this job completed by @Serranya/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat 0crat removed the scope label May 23, 2019
@0crat
Copy link
Collaborator

0crat commented May 23, 2019

The job #979 is now out of scope

@0crat
Copy link
Collaborator

0crat commented May 23, 2019

Pull request #979 was not merged, no payment for ARC, see §28

@sereshqua
Copy link

@Serranya did you make code review at all? I don't see your comments and also i don't see these problems fixed; @zCRUSADERz am I missing smth?

@zCRUSADERz
Copy link
Contributor Author

@sereshqua I have not fully studied the problem, so I closed the PR until I correct the shortcomings

@sereshqua
Copy link

@zCRUSADERz The job is closed only when the reported problem is solved

@sereshqua
Copy link

@0crat quality good bad

@0crat
Copy link
Collaborator

0crat commented May 24, 2019

Quality review completed: +4 point(s) just awarded to @sereshqua/z

@0crat
Copy link
Collaborator

0crat commented May 24, 2019

Order was finished, quality is "good": +25 point(s) just awarded to @Serranya/z

@zCRUSADERz
Copy link
Contributor Author

@sereshqua I thought to reopen PR when I correct the shortcomings. Now I need to open a new PR?

@sereshqua
Copy link

@zCRUSADERz oops, i just noticed TYPO in quality result, it should have been bad; I believe new issue needs to be opened if this is not solved

@Serranya
Copy link
Contributor

@sereshqua I did not do a quality review. The PR was retracted before that.

@sereshqua
Copy link

@Serranya well, then it is a zerocrat bug... it was assigned to me to check your work

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

Successfully merging this pull request may close these issues.

None yet

4 participants