[Pharo-project] Squeak bugs, Pharo bugs
Hi. I am wondering what the process is of filing bugs against Pharo/Squeak, notably ones already in Squeak mantis. This bug against Networking is longstanding, and has a fix: http://bugs.squeak.org/view.php?id=6768 Should I try to get it into Pharo? Is there a list of Mantis issues that have been folded into Pharo? Is there a process to determine which mantis bugs apply to Pharo? I ask because Pharo is currently, de facto, the only work being done on Squeak core, and I don't see a good reason to really push a separate effort and call it 3.11. So, how are you using squeak mantis in Pharo? -- Matthew Fulmer -- http://mtfulmer.wordpress.com/
On Fri, Jun 27, 2008 at 9:47 AM, Matthew Fulmer <tapplek@gmail.com> wrote:
Hi. I am wondering what the process is of filing bugs against Pharo/Squeak, notably ones already in Squeak mantis. This bug against Networking is longstanding, and has a fix:
http://bugs.squeak.org/view.php?id=6768
Should I try to get it into Pharo?
Is there a list of Mantis issues that have been folded into Pharo?
Is there a process to determine which mantis bugs apply to Pharo?
I ask because Pharo is currently, de facto, the only work being done on Squeak core, and I don't see a good reason to really push a separate effort and call it 3.11.
So, how are you using squeak mantis in Pharo?
If there is a report on mantis that you would like to see fixed in Pharo, add an entry to the issue tracking system at http://code.google.com/p/pharo with a link to the mantis report. If a fix exists, publish the package to the PharoInbox after having verify that the mcz can be loaded in a clean Pharo image. Set the status of your report as Fixed and the type to Patch. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
Hi Matthew, Every change needs an entry on our issue tracker http://code.google.com/p/pharo/ . For fixes originating in Mantis, just add a link to the Mantis issue there. We should consider adding a note to Mantis when a fix was integrated in Pharo. To contribute code, the process is described here: http://code.google.com/p/pharo/wiki/HowToContribute We planned to go through Mantis and select changes to be integrated in Pharo in the next weeks. If you have Mantis fixes that you would like to see applied, please provide a list. Adrian On Jun 27, 2008, at 09:47 , Matthew Fulmer wrote:
Hi. I am wondering what the process is of filing bugs against Pharo/Squeak, notably ones already in Squeak mantis. This bug against Networking is longstanding, and has a fix:
http://bugs.squeak.org/view.php?id=6768
Should I try to get it into Pharo?
Is there a list of Mantis issues that have been folded into Pharo?
Is there a process to determine which mantis bugs apply to Pharo?
I ask because Pharo is currently, de facto, the only work being done on Squeak core, and I don't see a good reason to really push a separate effort and call it 3.11.
So, how are you using squeak mantis in Pharo?
-- Matthew Fulmer -- http://mtfulmer.wordpress.com/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Fri, 2008-06-27 at 00:47 -0700, Matthew Fulmer wrote:
Hi. I am wondering what the process is of filing bugs against Pharo/Squeak, notably ones already in Squeak mantis. This bug against Networking is longstanding, and has a fix:
http://bugs.squeak.org/view.php?id=6768
Should I try to get it into Pharo?
Is there a list of Mantis issues that have been folded into Pharo?
No, but I don't think there are that many. But the question is still good. We had a good (but short) thread on squeak-dev about sharing fixes between forks but without a real outcome. I would like to see a matrix where every acknowledged fix will be put in and every fork can have a look at and decide to integrate or not.
Is there a process to determine which mantis bugs apply to Pharo?
Yes, we decided to double the effort and open tickets in pharo to put fixes from mantis into pharo. If I think once more about it I would create a new issues type mantis. This way we would have a change to find mantis fixes afterwards. As long as there isn't a good solution it is useful to find everything which is already included. I would propose that an issue from mantis is an issue with type "mantis" and status "fixed". That would fit into our "to be created" workflow. Using the mantis ticket number in the issue title will give all information that is needed.
I ask because Pharo is currently, de facto, the only work being done on Squeak core, and I don't see a good reason to really push a separate effort and call it 3.11.
I don't think that pharo is able to find a broader base on squeak-dev. It is good to have it separate. As soon as etoys is out this definite ;) For me it is just a question how we deal with the other way: bringing fixes from pharo back to squeak. I hope it is enough if squeak releasers scan the pharo issue tracker.
So, how are you using squeak mantis in Pharo?
We don't use mantis we just point to it. Norbert
On Fri, Jun 27, 2008 at 10:21:33AM +0200, Adrian Lienhard wrote:
Hi Matthew,
Every change needs an entry on our issue tracker http://code.google.com/p/pharo/ . For fixes originating in Mantis, just add a link to the Mantis issue there. We should consider adding a note to Mantis when a fix was integrated in Pharo.
I would suggest creating an issue in mantis named "Fixes incorperated into Pharo 0.1, and marking all incorperated issues as children of that one. That way, mantis will have an easily searchable record of what has been incorperated into Pharo.
To contribute code, the process is described here: http://code.google.com/p/pharo/wiki/HowToContribute
We planned to go through Mantis and select changes to be integrated in Pharo in the next weeks. If you have Mantis fixes that you would like to see applied, please provide a list.
ok. Thanks. I will do so soon. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/
Sure please do! The crew already answered. This is a cool feeling. Stef On Jun 27, 2008, at 9:47 AM, Matthew Fulmer wrote:
Hi. I am wondering what the process is of filing bugs against Pharo/Squeak, notably ones already in Squeak mantis. This bug against Networking is longstanding, and has a fix:
http://bugs.squeak.org/view.php?id=6768
Should I try to get it into Pharo?
Is there a list of Mantis issues that have been folded into Pharo?
Is there a process to determine which mantis bugs apply to Pharo?
I ask because Pharo is currently, de facto, the only work being done on Squeak core, and I don't see a good reason to really push a separate effort and call it 3.11.
So, how are you using squeak mantis in Pharo?
-- Matthew Fulmer -- http://mtfulmer.wordpress.com/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Jun 27, 2008, at 10:56 , Matthew Fulmer wrote:
On Fri, Jun 27, 2008 at 10:21:33AM +0200, Adrian Lienhard wrote:
Hi Matthew,
Every change needs an entry on our issue tracker http://code.google.com/p/pharo/ . For fixes originating in Mantis, just add a link to the Mantis issue there. We should consider adding a note to Mantis when a fix was integrated in Pharo.
I would suggest creating an issue in mantis named "Fixes incorperated into Pharo 0.1, and marking all incorperated issues as children of that one. That way, mantis will have an easily searchable record of what has been incorperated into Pharo.
If it is as simple as adding a note (I don't know), then this may be a good solution. I'll check when we start integrating changes. What I want to avoid, though, is that we increase our administrative work. Adrian
Hi Matthew,
Every change needs an entry on our issue tracker http://code.google.com/p/pharo/ . For fixes originating in Mantis, just add a link to the Mantis issue there. We should consider adding a note to Mantis when a fix was integrated in Pharo.
I would suggest creating an issue in mantis named "Fixes incorperated into Pharo 0.1, and marking all incorperated issues as children of that one. That way, mantis will have an easily searchable record of what has been incorperated into Pharo.
Yes!
To contribute code, the process is described here: http://code.google.com/p/pharo/wiki/HowToContribute
We planned to go through Mantis and select changes to be integrated in Pharo in the next weeks. If you have Mantis fixes that you would like to see applied, please provide a list.
ok. Thanks. I will do so soon.
Excellent. Matthew, we are open to people ideas :) We are just fed up about dogma like Etoys should be in the distribution. :)
yes but ou will read the fix notes on mantis anyway. Stef On Jun 27, 2008, at 12:55 PM, Adrian Lienhard wrote:
On Jun 27, 2008, at 10:56 , Matthew Fulmer wrote:
On Fri, Jun 27, 2008 at 10:21:33AM +0200, Adrian Lienhard wrote:
Hi Matthew,
Every change needs an entry on our issue tracker http://code.google.com/p/pharo/ . For fixes originating in Mantis, just add a link to the Mantis issue there. We should consider adding a note to Mantis when a fix was integrated in Pharo.
I would suggest creating an issue in mantis named "Fixes incorperated into Pharo 0.1, and marking all incorperated issues as children of that one. That way, mantis will have an easily searchable record of what has been incorperated into Pharo.
If it is as simple as adding a note (I don't know), then this may be a good solution. I'll check when we start integrating changes. What I want to avoid, though, is that we increase our administrative work.
Adrian
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (5)
-
Adrian Lienhard -
Damien Cassou -
Matthew Fulmer -
Norbert Hartl -
Stéphane Ducasse