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

pom.xml:46-49: Upgrade to Junit5. Finish JUnit upgrade to... #1030

Open
0pdd opened this issue Feb 8, 2019 · 21 comments
Open

pom.xml:46-49: Upgrade to Junit5. Finish JUnit upgrade to... #1030

0pdd opened this issue Feb 8, 2019 · 21 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented Feb 8, 2019

The puzzle 1019-4869c92c from #1019 has to be resolved:

https://github.com/teamed/qulice/blob/d1094351ef4d2b272606cf65333976f9a25e19dd/qulice-maven-plugin/pom.xml#L46-L49

The puzzle was created by Paulo Lobo on 07-Feb-19.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0crat
Copy link
Collaborator

0crat commented Feb 8, 2019

@krzyk/z please, pay attention to this issue

@0crat 0crat added the scope label Feb 8, 2019
@0crat
Copy link
Collaborator

0crat commented Feb 8, 2019

Job #1030 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Feb 8, 2019

The job #1030 assigned to @paulodamaso/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 24, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 1, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 6, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 11, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 16, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 21, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 26, 2019

@krzyk/z everybody who has role DEV is banned at #1030; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@krzyk
Copy link
Collaborator

krzyk commented Apr 30, 2019

@0crat assing @zCRUSADERz

@0crat
Copy link
Collaborator

0crat commented Apr 30, 2019

@0crat assing @zCRUSADERz (here)

@krzyk Can't understand "assing", try one of these:

  • assign Assign a performer to this issue
  • boost Set a boost for the job
  • continue Remove a job's impediment
  • hello Just say hello
  • in Register this issue in scope (WBS)
  • out Close the order and remove this job from scope
  • pay Pay a user some extra cash
  • quality Review a task
  • resign Resign from this issue
  • status Check the status of the job
  • version Print current version of the bot
  • wait Register an impediment for a job

@krzyk
Copy link
Collaborator

krzyk commented Apr 30, 2019

@0crat assign @zCRUSADERz

@0crat
Copy link
Collaborator

0crat commented Apr 30, 2019

@0crat assign @zCRUSADERz (here)

@krzyk The job #1030 assigned to @zCRUSADERz/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; @zCRUSADERz/z is not a member of this project yet, but they can request to join, as §1 explains; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Apr 30, 2019

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @krzyk/z

@zCRUSADERz
Copy link
Contributor

@0crat wait for review

@0crat 0crat added the waiting label May 9, 2019
@0crat
Copy link
Collaborator

0crat commented May 9, 2019

@0crat wait for review (here)

@zCRUSADERz The impediment for #1030 was registered successfully by @zCRUSADERz/z

@0crat
Copy link
Collaborator

0crat commented May 9, 2019

@0crat wait for review (here)

@zCRUSADERz Job #1030 is not in the agenda of @zCRUSADERz/z, can't set impediment

@zCRUSADERz
Copy link
Contributor

@0crat status

@0crat
Copy link
Collaborator

0crat commented May 9, 2019

@0crat status (here)

@zCRUSADERz This is what I know about this job in C3T49A35L, as in §32:

@yegor256 yegor256 removed pdd labels Apr 16, 2024
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