[Issue tracker] Please have a look at your issues!
Hi, We should do a pass over all issues. e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue? You can get a list of *all* open issues: https://pharo.fogbugz.com/f/filters/33/All-Opened or just the ones for 2.0: https://pharo.fogbugz.com/f/filters/8/2-0-Work-Needed and 3.0: https://pharo.fogbugz.com/f/filters/37/3-0-Work-Needed For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?) Marcus
Done. I've resolved the one that was opened by me. On Fri, Jul 5, 2013 at 9:00 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
Hi,
We should do a pass over all issues.
e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue?
You can get a list of *all* open issues:
https://pharo.fogbugz.com/f/filters/33/All-Opened
or just the ones for 2.0:
https://pharo.fogbugz.com/f/filters/8/2-0-Work-Needed
and 3.0:
https://pharo.fogbugz.com/f/filters/37/3-0-Work-Needed
For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?)
Marcus
(Well, actually it was Camillo who opened and fixed while pair-programming this Monday) On Fri, Jul 5, 2013 at 12:59 PM, Martin Dias <tinchodias@gmail.com> wrote:
Done. I've resolved the one that was opened by me.
On Fri, Jul 5, 2013 at 9:00 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
Hi,
We should do a pass over all issues.
e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue?
You can get a list of *all* open issues:
https://pharo.fogbugz.com/f/filters/33/All-Opened
or just the ones for 2.0:
https://pharo.fogbugz.com/f/filters/8/2-0-Work-Needed
and 3.0:
https://pharo.fogbugz.com/f/filters/37/3-0-Work-Needed
For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?)
Marcus
Le 05/07/2013 09:00, Marcus Denker a écrit :
Hi,
We should do a pass over all issues.
e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue?
You can get a list of *all* open issues:
https://pharo.fogbugz.com/f/filters/33/All-Opened
or just the ones for 2.0:
All the 2.0 backports I have been looking at have fixes waiting for review... I'm using the fixes on a daily basis (loading by hand the relevant SLICES).
and 3.0:
For those I'm involved in, I don't have access rights to upload SLICES, so I have stored them under http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main. (loading by hand the slices, otherwise 3.0 does not even work at all for me). Thierry
For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?)
Marcus
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
On Jul 5, 2013, at 1:14 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Le 05/07/2013 09:00, Marcus Denker a écrit :
All the 2.0 backports I have been looking at have fixes waiting for review... I'm using the fixes on a daily basis (loading by hand the relevant SLICES).
Yes, it would be nice if someone would look at them.
and 3.0:
For those I'm involved in, I don't have access rights to upload SLICES, so I have stored them under http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main. (loading by hand the slices, otherwise 3.0 does not even work at all for me).
I -> copied them over -> added a not to the bug entries -> put those to "review needed" -> Added you to the Pharo team so you can commit directly (it is on the TODO so that there is an inbox where everyone can commit Marcus
Thanks Marcus for all that! Thierry Le 05/07/2013 15:10, Marcus Denker a écrit :
On Jul 5, 2013, at 1:14 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Le 05/07/2013 09:00, Marcus Denker a écrit :
All the 2.0 backports I have been looking at have fixes waiting for review... I'm using the fixes on a daily basis (loading by hand the relevant SLICES).
Yes, it would be nice if someone would look at them.
and 3.0:
For those I'm involved in, I don't have access rights to upload SLICES, so I have stored them under http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main. (loading by hand the slices, otherwise 3.0 does not even work at all for me).
I -> copied them over -> added a not to the bug entries -> put those to "review needed" -> Added you to the Pharo team so you can commit directly (it is on the TODO so that there is an inbox where everyone can commit
Marcus
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Thierry I will add you to the pharo team SmalltalkHub will support public inbox soon! Stef On Jul 5, 2013, at 1:19 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Le 05/07/2013 09:00, Marcus Denker a écrit :
Hi,
We should do a pass over all issues.
e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue?
You can get a list of *all* open issues:
https://pharo.fogbugz.com/f/filters/33/All-Opened
or just the ones for 2.0:
All the 2.0 backports I have been looking at have fixes waiting for review... I'm using the fixes on a daily basis (loading by hand the relevant SLICES).
and 3.0:
For those I'm involved in, I don't have access rights to upload SLICES, so I have stored them under http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main. (loading by hand the slices, otherwise 3.0 does not even work at all for me).
Thierry
For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?)
Marcus
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Thanks Stephane, Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces@lists.pharo.org] de la part de Stéphane Ducasse [stephane.ducasse@inria.fr] Date d'envoi : samedi 6 juillet 2013 10:56 à : Pharo Development List Objet : Re: [Pharo-dev] [Issue tracker] Please have a look at your issues! Thierry I will add you to the pharo team SmalltalkHub will support public inbox soon! Stef On Jul 5, 2013, at 1:19 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Le 05/07/2013 09:00, Marcus Denker a écrit :
Hi,
We should do a pass over all issues.
e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue?
You can get a list of *all* open issues:
https://pharo.fogbugz.com/f/filters/33/All-Opened
or just the ones for 2.0:
All the 2.0 backports I have been looking at have fixes waiting for review... I'm using the fixes on a daily basis (loading by hand the relevant SLICES).
and 3.0:
For those I'm involved in, I don't have access rights to upload SLICES, so I have stored them under http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main. (loading by hand the slices, otherwise 3.0 does not even work at all for me).
Thierry
For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?)
Marcus
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
participants (5)
-
GOUBIER Thierry -
Goubier Thierry
-
Marcus Denker -
Martin Dias -
Stéphane Ducasse