-
Notifications
You must be signed in to change notification settings - Fork 156
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
1.58 #1013
Comments
@original-brownbear milestone set to |
@yegor256 before writing up the report here, anything you'd like to see handled with priority? |
@original-brownbear nope, I don't have any priorities. maybe that problem with |
@yegor256 @alex-palevsky given that the last release was 1.57 on Aug 23, 2015 and the latest ReportI will provide scope status in a few hours, I thought the below should be reported asap though. Issues
Risks
|
@original-brownbear looks perfect, many thanks! |
@original-brownbear could you please pick this up? This article explains how we work. Any technical questions you may ask right here The budget of this issue is 30 mins, which is exactly how much will be paid when the task is done (see this for explanation) |
@alex-palevsky on it already :) |
@rultor release tag is |
@original-brownbear OK, I will release it now. Please check the progress here |
@alex-palevsky @original-brownbear Oops, I failed. You can see the full log here (spent 11min)
|
@rultor release tag is |
@original-brownbear OK, I will release it now. Please check the progress here |
@original-brownbear Done! FYI, the full log is here (took me 59min) |
@original-brownbear thanks |
@alex-palevsky I need your help here :) , the only thing open and without a proper PR is #960 requiring action on your end. |
@alex-palevsky another thing: We need to move the milestone 2.0. It has been overdue for months now. Extrapolating from the number of tickets being resolved lately and the number of open tickets, I suggest to move it 2 months into the future starting from today. |
@yegor256 @alex-palevsky
Issues
Risks
|
@original-brownbear thanks for the update! |
@alex-palevsky sorry, I feel the need to defend myself here :)
I asked you to move the milestone #1013 (comment), I think this is the best I can do given that the milestone was already missed when I started as an architect here. Not dispatched issues: About the stuck tasks: Not a big deal either way :), just asking how I could have addressed things better here? |
@rultor release tag is |
@original-brownbear OK, I will release it now. Please check the progress here |
@alex-palevsky @original-brownbear Oops, I failed. You can see the full log here (spent 7min)
|
@rultor release tag is |
@original-brownbear OK, I will release it now. Please check the progress here |
@original-brownbear Done! FYI, the full log is here (took me 53min) |
@yegor256 Release |
@original-brownbear yes, we're good |
@alex-palevsky mark release 1.61.8 as final |
@yegor256 right, release 1.61.8 is set to "final" |
@original-brownbear please, pay attention to this (par.33):
-25 added to your rating, at the moment it is: +619 |
@alex-palevsky please move milestone 2.0 to April 28th. |
@original-brownbear sure, milestone set to 2.0 |
@alex-palevsky please close this, it's still open in my agenda :) |
@original-brownbear I will close it when there is a new release published |
@alex-palevsky Sorry I don't understand |
@original-brownbear Closing.. |
@original-brownbear 31 mins was added to your account, many thanks for your contribution (payment AP-33L476332W905053B)! The task took 284 hours and 43 mins.. here is how the bonus is calculated: t=4604, c=228, h=3833, diff=1.57..master. +31 added to your rating, at the moment it is: +903 |
Please, publish a new release 1.58 (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: