[Pharo-project] Something does not work with issue tracker status
Hi guys. Previously, we use to mark issues as "Fixed" once someone proposed a solution. Now we have to first put it as ""FixReviewNeeded" and then when someone else takes the time to review it put it as "FixToInclude". Now...the problem is that nobody reviews and issues get outdated. And then, when trying to load the slice or .cs it does not work anyomre, or it is outdated, or whatever. Meaning that it has to be regenerated and we spend the double of time. So, what can we do to improve this???? ideas: 1) We should be more confident ourselves. Imagine we have proposed something and it is as "FixReviewNeeded". If we have run the tests, and we didn't break anything, and the problem is really fixed, and the topic is not something REALLY critical, and no one has reviewed your issue, why not to putting it as "FixToInclude" ? 2) We really need people helping review changes. There are only a few guys that do this. You DON'T need to be an expert. "FixReviewNeeded" does not mean "HasToBeReviewedByAGuruExperiencedHacker". It just means "it just requires another eyes". So, please, help us review issues. Is the only way to improve. so, what do you think? -- Mariano http://marianopeck.wordpress.com
Mariano Martinez Peck wrote
We really need people helping review changes... So, please, help us review issues. Is the only way to improve.
+1. I will try a few... Sean -- View this message in context: http://forum.world.st/Something-does-not-work-with-issue-tracker-status-tp46... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Why not organize "feature teams" along packages or package sets on which experts have approval power? Of course, some stuff will be cross packages but still, it should work. Is there any chart or trend in there, like bugs unfixed since x days that should be? Phil 2012/6/6 Sean P. DeNigris <sean@clipperadams.com>
Mariano Martinez Peck wrote
We really need people helping review changes... So, please, help us
review
issues. Is the only way to improve.
+1. I will try a few...
Sean
-- View this message in context: http://forum.world.st/Something-does-not-work-with-issue-tracker-status-tp46... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges
we should first get the test monkey up and running... that will take a lot of work an assures that at least the existing tests won't fail!
On 6 June 2012 23:40, Camillo Bruni <camillobruni@gmail.com> wrote:
we should first get the test monkey up and running... that will take a lot of work an assures that at least the existing tests won't fail!
yes. and second thing, even if we integrate half-backed solution, we can always fix it on next iteration, if it causing problems.. like that it will be some progress comparing to indefinite time when issue needs to be reviewed. but sure thing, for changes which can really screw things up, we need serious review before integration. -- Best regards, Igor Stasenko.
participants (5)
-
Camillo Bruni -
Igor Stasenko -
Mariano Martinez Peck -
phil＠highoctane.be -
Sean P. DeNigris