Timeline for Colleague fixes my bugs
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2020 at 4:50 | answer | added | Momo | timeline score: 0 | |
| Dec 1, 2019 at 23:18 | answer | added | Koenigsberg | timeline score: 3 | |
| Dec 1, 2019 at 3:39 | history | became hot network question | |||
| Nov 30, 2019 at 20:00 | review | Close votes | |||
| Dec 2, 2019 at 22:23 | |||||
| Nov 30, 2019 at 19:58 | comment | added | Peter M | @Jesse_b In general for an unknown system that may be true but the OP and the OPs QA seemed to think that it was minor and that it was not an issue that would postpone release. | |
| Nov 30, 2019 at 19:57 | comment | added | nemezis | @PeterM yes, we do. | |
| Nov 30, 2019 at 19:56 | comment | added | Peter M | Do you have a formal bug system where issues are assigned to individual developers? Because if your coworker is working on things that are formally assigned to you then that is a different matter. | |
| Nov 30, 2019 at 19:56 | vote | accept | nemezis | ||
| Nov 30, 2019 at 19:55 | comment | added | jesse_b | @PeterM: disagree. It's great that it passes but if a bug is found friday before the release, the release should have been postponed because a half day probably isn't enough time to even do proper tests. | |
| Nov 30, 2019 at 19:53 | comment | added | Peter M | @Jesse_b If the code passes all QA tests then it doesn't matter if that happens 1 millisecond or 1 month before release. | |
| Nov 30, 2019 at 19:51 | answer | added | gnasher729 | timeline score: 12 | |
| Nov 30, 2019 at 19:48 | comment | added | jesse_b | I think you're being a little cavalier with timelines, or maybe your company is. Code shouldn't be still in testing on the day of release. | |
| Nov 30, 2019 at 19:47 | comment | added | nemezis | No, I did not. We discussed with QA in the same chat that the issue can wait till Monday. It is not like we were planning to ship it first thing Monday morning. | |
| Nov 30, 2019 at 19:44 | comment | added | jesse_b | Did you provide a timeline when you would be able to fix it? I think it's possible they were expecting the fix well before Sunday night. | |
| Nov 30, 2019 at 19:41 | comment | added | nemezis | @Jesse_b, you are right. Thanks | |
| Nov 30, 2019 at 19:41 | history | edited | nemezis | CC BY-SA 4.0 |
clarified that colleague agreed that I will be fixing this code before release
|
| Nov 30, 2019 at 19:37 | answer | added | jesse_b | timeline score: 17 | |
| Nov 30, 2019 at 19:37 | comment | added | nemezis | It is more about my wasted time - I wouldn't start working on a fix knowing that someone else is trying to fix it. | |
| Nov 30, 2019 at 19:30 | comment | added | nemezis | He did, but after that I've replied that I will look into it, and he agreed | |
| Nov 30, 2019 at 19:30 | review | First posts | |||
| Dec 1, 2019 at 0:27 | |||||
| Nov 30, 2019 at 19:29 | comment | added | jesse_b | Didn't he notify you of his intentions when he said that he will look into it in slack? | |
| Nov 30, 2019 at 19:26 | history | asked | nemezis | CC BY-SA 4.0 |