Help needed: old issues issue tracker entries
Hi, The issue tracker has 658 open issues. This number is more or less constant. We are fixing and integrating *a lot*, alone the last 7 days we managed to close 89 issue tracker entries. But the older entries see not much work. Of course one reason is that everything fixable gets fixed and only hard cases remain⦠but cases can be âdifficultâ for many reasons. I would be nice if everyone could help and have a look at older issues: -> Still relevant? -> Maybe already fixed? -> Is the description good? -> What is the next action that needs to be done? And keep in mind that the issue tracker is not a TODO list. If you see something odd and put and issue âoh, this looks oddâ but there is no action for a year, does it really make sense to keep that issue open? Every open issue takes energy away from the others. So please check if issues make sense of this kind: -> âIt would be nice ifâ but not even important enough for the submitter to do -> TODO issues that are huge projects in themselves -> â¦. It would be nice if *you* would check the issue that you have been involved with the last months and see what is needed to solve them. Marcus
Case 16725 - Merge changes from spec github repository. 2 subcases are resolved, 2 other need decision. Nothing time-consuming - just decide if we integrate them or mark as wontfix. Case 15927 - Menu is broken when contained in a list. This is much more complicated, it's even not clear which class (TransfromMorph or MenuItemMorph) is bugged. I tried to fix it myself, but had no success. -- View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp4864269... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
I had an issue assigned against me, which I have not the time nor the knowledge to fix. (Inconstant aspect ratio of Desktop background image). Can I suggest it is given to someone who knows the Desktop GUI codebase? (If I was in a position to fix it, I would have just submitted a fix, not a bug report) On 2 December 2015 at 13:42, webwarrior <reg@webwarrior.ws> wrote:
Case 16725 - Merge changes from spec github repository. 2 subcases are resolved, 2 other need decision. Nothing time-consuming - just decide if we integrate them or mark as wontfix.
Case 15927 - Menu is broken when contained in a list. This is much more complicated, it's even not clear which class (TransfromMorph or MenuItemMorph) is bugged. I tried to fix it myself, but had no success.
-- View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp4864269... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Am 03.12.2015 1:08 vorm. schrieb "EuanM" <euanmee@gmail.com>:
I had an issue assigned against me, which I have not the time nor the knowledge to fix.
(Inconstant aspect ratio of Desktop background image).
Can I suggest it is given to someone who knows the Desktop GUI codebase?
(If I was in a position to fix it, I would have just submitted a fix, not a bug report)
It was assigned to "everyone". And just assigned to you after a fix was provided. That issue is already closed.
On 2 December 2015 at 13:42, webwarrior <reg@webwarrior.ws> wrote:
Case 16725 - Merge changes from spec github repository. 2 subcases are resolved, 2 other need decision. Nothing time-consuming - just decide if we integrate them or mark as wontfix.
Case 15927 - Menu is broken when contained in a list. This is much more complicated, it's even not clear which class (TransfromMorph or MenuItemMorph) is bugged. I tried to fix it myself, but had no success.
-- View this message in context:
http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp4864269...
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Excellent. Can I suggest that in future they are simply closed, rather than re-assigned? On 3 December 2015 at 06:35, Nicolai Hess <nicolaihess@gmail.com> wrote:
Am 03.12.2015 1:08 vorm. schrieb "EuanM" <euanmee@gmail.com>:
I had an issue assigned against me, which I have not the time nor the knowledge to fix.
(Inconstant aspect ratio of Desktop background image).
Can I suggest it is given to someone who knows the Desktop GUI codebase?
(If I was in a position to fix it, I would have just submitted a fix, not a bug report)
It was assigned to "everyone". And just assigned to you after a fix was provided. That issue is already closed.
On 2 December 2015 at 13:42, webwarrior <reg@webwarrior.ws> wrote:
Case 16725 - Merge changes from spec github repository. 2 subcases are resolved, 2 other need decision. Nothing time-consuming - just decide if we integrate them or mark as wontfix.
Case 15927 - Menu is broken when contained in a list. This is much more complicated, it's even not clear which class (TransfromMorph or MenuItemMorph) is bugged. I tried to fix it myself, but had no success.
-- View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp4864269... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On Wed, Dec 9, 2015 at 9:35 AM, EuanM <euanmee@gmail.com> wrote:
Excellent. Can I suggest that in future they are simply closed, rather than re-assigned?
The reassignment happens automatically in the background whenever an issue is "resolved". Its a part of Fogbugz we have no control over. cheers -ben
On 3 December 2015 at 06:35, Nicolai Hess <nicolaihess@gmail.com> wrote:
Am 03.12.2015 1:08 vorm. schrieb "EuanM" <euanmee@gmail.com>:
I had an issue assigned against me, which I have not the time nor the knowledge to fix.
(Inconstant aspect ratio of Desktop background image).
Can I suggest it is given to someone who knows the Desktop GUI codebase?
(If I was in a position to fix it, I would have just submitted a fix, not a bug report)
It was assigned to "everyone". And just assigned to you after a fix was provided. That issue is already closed.
On 2 December 2015 at 13:42, webwarrior <reg@webwarrior.ws> wrote:
Case 16725 - Merge changes from spec github repository. 2 subcases are resolved, 2 other need decision. Nothing time-consuming - just decide if we integrate them or mark as wontfix.
Case 15927 - Menu is broken when contained in a list. This is much more complicated, it's even not clear which class (TransfromMorph or MenuItemMorph) is bugged. I tried to fix it myself, but had no success.
-- View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp4864269... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 30 Nov 2015, at 13:21, marcus.denker@inria.fr wrote:
Hi,
The issue tracker has 658 open issues. This number is more or less constant.
down to 642! (of course we closed more than that, we are at more than 6 per day closed, but the thing is that new ones get open, too) With >600 issues open, if someone adds a comment in the sense of âthis can be closedâ, can you send me (or the List) a mail? Or put the issue on âfixedâ ? The problem is that with >600 issues, even an issue that is clearly commented as fixed has a very low chance of someone reading the note and closing the entry within any reasonable time frame if we rely on someone stumbling on it by chance... Marcus
On 05 Dec 2015, at 19:31, Marcus Denker <marcus.denker@inria.fr> wrote:
On 30 Nov 2015, at 13:21, marcus.denker@inria.fr wrote:
Hi,
The issue tracker has 658 open issues. This number is more or less constant.
down to 642!
Down to 638. Can *YOU* help to get it to 637? Marcus
Thanks a lot, Marcus for this encouragements! Doru
On Dec 7, 2015, at 6:15 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On 05 Dec 2015, at 19:31, Marcus Denker <marcus.denker@inria.fr> wrote:
On 30 Nov 2015, at 13:21, marcus.denker@inria.fr wrote:
Hi,
The issue tracker has 658 open issues. This number is more or less constant.
down to 642!
Down to 638. Can *YOU* help to get it to 637?
Marcus
-- www.tudorgirba.com "We cannot reach the flow of things unless we let go."
The over 600 number looks scary sometimes.. but just by doing one after the other, we it is actually doable. The proof is that we closed 1587 already for Pharo5⦠and for Pharo all versions we are at 14295 issues âdoneâ. 638 looks small compared to that. Marcus
On 07 Dec 2015, at 12:30, Tudor Girba <tudor@tudorgirba.com> wrote:
Thanks a lot, Marcus for this encouragements!
Doru
On Dec 7, 2015, at 6:15 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On 05 Dec 2015, at 19:31, Marcus Denker <marcus.denker@inria.fr> wrote:
On 30 Nov 2015, at 13:21, marcus.denker@inria.fr wrote:
Hi,
The issue tracker has 658 open issues. This number is more or less constant.
down to 642!
Down to 638. Can *YOU* help to get it to 637?
Marcus
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Can *YOU* help to get it to 637?
Without activity/reply for some time and no clear action --- maybe close as stale?: * https://pharo.fogbugz.com/f/cases/10047/Regex-not-independant-of-platform * https://pharo.fogbugz.com/f/cases/13479/ValueHolder-and-NewValueHolder-do-no... * https://pharo.fogbugz.com/f/cases/14500/Manual-class-replacement-unwanted-ob... * https://pharo.fogbugz.com/f/cases/15098/Default-button-size How do I push VM change?: * https://pharo.fogbugz.com/f/cases/14759/Linux-X11-VM-default-encoding-should... -- Peter
On 07 Dec 2015, at 13:42, Peter Uhnak <i.uhnak@gmail.com> wrote:
Can *YOU* help to get it to 637?
Without activity/reply for some time and no clear action --- maybe close as stale?:
* https://pharo.fogbugz.com/f/cases/10047/Regex-not-independant-of-platform * https://pharo.fogbugz.com/f/cases/13479/ValueHolder-and-NewValueHolder-do-no... * https://pharo.fogbugz.com/f/cases/14500/Manual-class-replacement-unwanted-ob... * https://pharo.fogbugz.com/f/cases/15098/Default-button-size
How do I push VM change?:
* https://pharo.fogbugz.com/f/cases/14759/Linux-X11-VM-default-encoding-should...
Iâlll review and accept it itâs been there from some time but I remember I didnât merge at the time for some reason⦠now I just forget what was (shame on me, I didnât take a note :( )⦠so I will re-review it :) Esteban
-- Peter
participants (9)
-
Ben Coman -
Esteban Lorenzano -
EuanM -
Marcus Denker -
marcus.denker＠inria.fr
-
Nicolai Hess -
Peter Uhnak -
Tudor Girba -
webwarrior