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

ListEnvelopeTest.java:43-45: Get rid of the Immutable in... #1217

Closed
0pdd opened this issue Nov 3, 2019 · 15 comments
Closed

ListEnvelopeTest.java:43-45: Get rid of the Immutable in... #1217

0pdd opened this issue Nov 3, 2019 · 15 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented Nov 3, 2019

The puzzle 898-0bea8a51 from #898 has to be resolved:

* @todo #898:30min Get rid of the Immutable in StringList nested class
* That's because this test should check the original behavior of ListEnvelope
* Now this test checks behavior of the Immutable decorator

The puzzle was created by @fanifieiev on 28-Oct-19.

Estimate: 30 minutes, role: DEV.

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 Nov 3, 2019

@paulodamaso/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Nov 3, 2019

Job #1217 is now in scope, role is DEV

@0crat 0crat added the scope label Nov 3, 2019
@0crat
Copy link
Collaborator

0crat commented Nov 3, 2019

The job #1217 assigned to @lavinj87/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 Jul 5, 2020

The architect of the project has changed; @paulodamaso/z is not at this role anymore; @victornoel/z is the architect now

@victornoel
Copy link
Collaborator

@0crat in

@0crat 0crat added the role/DEV label Jul 5, 2020
@0crat
Copy link
Collaborator

0crat commented Jul 6, 2020

The job #1217 assigned to @Roman-Kuvaldin/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

@victornoel
Copy link
Collaborator

@0crat refuse

1 similar comment
@victornoel
Copy link
Collaborator

@0crat refuse

@0crat
Copy link
Collaborator

0crat commented Jul 15, 2020

@0crat refuse (here)

@victornoel Job gh:yegor256/cactoos#1217 is not assigned, can't get performer

@0crat
Copy link
Collaborator

0crat commented Jul 15, 2020

@0crat refuse (here)

@victornoel The user @Roman-Kuvaldin/z resigned from #1217, please stop working. Reason for job resignation: Order was cancelled

@0crat
Copy link
Collaborator

0crat commented Aug 8, 2020

The job #1217 assigned to @mazdack/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

@victornoel
Copy link
Collaborator

@0crat refuse

@0crat
Copy link
Collaborator

0crat commented Aug 23, 2020

@0crat refuse (here)

@victornoel The user @mazdack/z resigned from #1217, please stop working. Reason for job resignation: Order was cancelled

@0crat
Copy link
Collaborator

0crat commented Sep 4, 2020

The job #1217 assigned to @andreoss/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

andreoss added a commit to andreoss/cactoos that referenced this issue Sep 5, 2020
andreoss added a commit to andreoss/cactoos that referenced this issue Sep 5, 2020
andreoss added a commit to andreoss/cactoos that referenced this issue Sep 6, 2020
andreoss added a commit to andreoss/cactoos that referenced this issue Sep 8, 2020
@0pdd 0pdd closed this as completed Sep 8, 2020
@0pdd
Copy link
Collaborator Author

0pdd commented Sep 8, 2020

The puzzle 898-0bea8a51 has disappeared from the source code, that's why I closed this issue.

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

3 participants