"This issue is also tracked by Pharo:
http://code.google.com/p/pharo/issues/detail?id=XY
"
So this comment does not say whether we eventually integrated it or
not (this can be simply found out by following the link). So the
comment can be added already earlier in the process, which makes it
easier.
Anybody has a better idea?
At the moment we track Mantis tickets that we are interested in. So
we link to Mantis. What purpose is served by linking back from
Mantis?
just so that if you look at Mantis you can easily see whether this
was treated in Pharo without needing to search in our issue tracker.
Maybe its not needed, I'm not sure.
I think that this is needed. I like to know in a glance that the issue
is done.
So I added harvested in pharo or evaluated and rejected for pharo.
So we can also go without it for now and if we see that it would be
nice to have the links, we can add them later.
Is there a possibility to get a listing of bugs that pharo isn't
aware of? I have some problems understanding the intended workflow.
I added the Mantis bug numbers to the title of each issue so we can
easily get an overview of the mantis tickets we track.
I think how you did it is exactly the right way.
However if we acknowledge on your proposal than the squeak issues
I created aren't the right way to do. A squeak version can include
many mantis tickets. If we like to integrate only some of them that
leads to confusion.
I don't think so. The link on Mantis would just be for convenience.
Say, you find an important fix on Mantis that was recently added and
you want to integrate it into Pharo. The note would then be
convenient to quickly see whether somebody else had already done this.
Btw. if I understand Stef correct than we shouldn't
try to integrate all 3.10 fixes but to really analyze what pharo
needs.
I agree. I would focus on the important ones.
Not only, the simple ones are cool too. :)
We need the good ones :) after the fixes of nicolas are also some that
we should look at.
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
