-
Notifications
You must be signed in to change notification settings - Fork 111
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
0.16 #604
Comments
@krzyk please proceed, it's yours |
@yegor256 what are your preferences for this release? |
@rultor release tag is |
@krzyk there are some issues (see par.33) in the project now: some tasks in the project are "stuck": #540 (20 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. added -25 to your rating, now it is equal to +3572 |
@rultor release tag is |
@davvd @krzyk Oops, I failed. You can see the full log here (spent 54min)
|
@rultor release tag is |
@rultor release tag is |
@yegor256 can ask @davvd to speed up a bit? It is quite frustrating for devs to wait for a review (bonuses). |
@krzyk there are a few issues by par.33: some tasks are stuck: #351 (389 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. -25 to your rating, your total score is +4212 |
@yegor256 another issue is that if I assign an issue that was created over 20 days ago, to anyone, David will come in few days and say that the task is stuck, but it is not stuck, it was just assigned. He should not look at issue creation time but when it was unpostponed or assigned. |
@rultor release tag is |
@krzyk pay attention to the following, as required in par.33: some tasks in the project are "stuck": #502 (69 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. -25 to your rating, your total score is +4886 |
@yegor256 all issues mentioned have been fixed, can I release 0.16? |
@krzyk yeah, let's do it |
@rultor release tag is |
@yegor256 please set |
@davvd release 0.16 is final |
@krzyk Thanks all, I am closing |
Please, publish a new release 0.16 (or higher). Don't forget to update us here regularly (at least once a week), as explained in this article.
The text was updated successfully, but these errors were encountered: