1.62

[alex-palevsky]

Please, publish a new release 1.62 (or higher). Don't forget to update us here regularly (at least once a week), as explained in this article.

[alex-palevsky]

@original-brownbear the task is yuors

[alex-palevsky]

@original-brownbear I set the milestone to 2.0 since there is nothing set yet

[original-brownbear]

@alex-palevsky please set the due date for milestone 2.0 to April 28th 2016.

[alex-palevsky]

@alex-palevsky please set the due date for milestone 2.0 to April 28th 2016.

@original-brownbear I set the milestone here to 2.0

[original-brownbear]

@yegor256 any wishes for this one ? :)
Also could you please help with moving the milestone, I keep spamming @alex-palevsky with this issue to no avail.
Thanks!

[yegor256]

@original-brownbear I fixed the milestone. I think this one is the most important: #832

[original-brownbear]

@yegor256 thanks!

[original-brownbear]

@yegor256 update :)

So for the next release 1.63 I'd go for:

• ReleaseBinaries.java:47-49: Implement attaching artifacts to release,... #832 as requested
• Rultor Uses the Target Branch's .rultor.yml on Merges #1039
• Deprecate Using the yegor256/rultor Docker Image for Other Projects #1018
• PR doesn't closed by Rultor #918
• Rultor should not ask architect to confirm merge on a closed PR #917
• rultor not timing out #1042
• Rultor "stop" command issues wrong/confusing messages #864
• Stop Command Acts on the Wrong Request In Some Cases #1050

Issues

1. Rultor EC2 instance issues, namely Docker daemon dying or running out of HD space are not recovered by Rultor itself. Please see Cannot connect to the Docker daemon #1041 :)
2. Developers have many issues with tasks related to the Docker side of things.
3. (Integration) tests are by far not comprehensive enough.
4. Rultor Uses the Target Branch's .rultor.yml on Merges #1039 allows repositories to get into a state where only manual action on master can resolve dependency issues with the build.

Risks

1. Using the default image (having a non-deterministic build) is widespread in other projects, adjusting Rultor dependencies may cause widespread issues similar to Deprecate Using the yegor256/rultor Docker Image for Other Projects #1018 [4,8]
2. EC2 Docker daemon could stop or run out of disk space, causing downtime until manually fixed Cannot connect to the Docker daemon #1041 :) [4,5]
3. We may fail to find developers capable to contribute to Docker related issues productively [9,4]
4. Tests are not safe enough[7,4]

[yegor256]

@original-brownbear thanks for the report, the scope of 1.63 sounds perfect

[alex-palevsky]

@original-brownbear there are some issues (see par.33) in the project now:

• some tasks are stuck: ReleaseBinaries.java:47-49: Implement attaching artifacts to release,... #832 (336 days), Private repos should not be shown if logged in user can't access them #773 (391 days), architect per command #806 (349 days), master is used instead of default repo branch #818 (343 days); please do something about it. There are basically three options: 1) mark some of them as "postponed" (see par.26), 2) re-assign them (see par.29), or 3) try to help their performers to resolve them.
• these issues are still not dispatched anyhow: RFE: Add rebase command #876. Either register as bugs or ask their reporters to close.

-25 added to your rating, at the moment it is: +1053

[original-brownbear]

@alex-palevsky I've dispatched #876 multiple times to no avail :) Please look into it.

[alex-palevsky]

@alex-palevsky I've dispatched #876 multiple times to no avail :) Please look into it.

@original-brownbear please, discuss each task in its own ticket. asking me here to look into some other ticket is rather confusing. when you need my attention in some ticket, ask me there.

[alex-palevsky]

@original-brownbear There are a few concerns (see par.33):

• some tasks in the project are "stuck": Private repos should not be shown if logged in user can't access them #773 (397 days); please do something about it ASAP. You basically have three options: 1) mark some of them as "postponed" (par.26), 2) re-assign them (par.29), or 3) try to help their performers to resolve them.
• there are way too many "urgent" tasks in the project (6), please de-prioritize some of them
• some issues were reported some time ago, but still not dispatched: RFE: Add rebase command #876. Please, do something about them. Either register as bugs or ask their reporters to close them.

added -25 to your rating, now it is equal to +1575

[alex-palevsky]

@original-brownbear There are a few problems in the project now, see par.33:

• some tasks in the project are "stuck": Private repos should not be shown if logged in user can't access them #773 (401 days), com.rultor.agents.github.qtn.QnByArchitect Classname is misleading, its Test Cases are Meaningless  #1028 (22 days); please do something about it ASAP. You basically have three options: 1) mark some of them as "postponed" (par.26), 2) re-assign them (par.29), or 3) try to help their performers to resolve them.
• there are way too many "urgent" tasks in the project (8), please de-prioritize some of them

-25 to your rating, your total score is +1813

[alex-palevsky]

@yegor256 Thanks, closing it now.

[0crat]

Oops! Job gh:yegor256/rultor#1043 was not in scope