On Jul 9, 2008, at 11:15 , Norbert Hartl wrote:
On Wed, 2008-07-09 at 10:53 +0300, Adrian Lienhard wrote:
My suggestion is that we add a comment in Mantis as follows:
"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. 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.
This way it would be better to get rid of the Type-squeak tickets and
to create a pharo issue Type_Mantis for every ticket we track. This
way
it would make sense to link back from mantis.
I think it works well how we started.
Cheers,
Adrian
Btw, I'm slowly going through your changes to verify them.
my 2 Rappen :)
Norbert
Adrian
On Jul 8, 2008, at 21:39 , Stéphane Ducasse wrote:
On Jul 8, 2008, at 4:58 PM, Adrian Lienhard wrote:
nice
Have we decided how we want to tag the Mantis issues that are
integrated in Pharo? I remember we discussed
- adding a comment, and
- having one empty issue of which all other issues are children.
oops I missed the second item
Adrian
On Jul 8, 2008, at 15:46 , Norbert Hartl wrote:
I played a little with the squeak and the mantis tickets.
First, I decided to use the usual way to indicate a mantis
bug number:
M1234.
This way it is easily distinguishable from other version
numbers. Then I changed the title of the mantis tickets
to follow the number convention.
M6355: [ENH] Lots of tests for Collections
I started to change the squeak issues to include the mantis
numbers in the title. It is in () at the end of the title. E.g.
7073 CollectionAndCollectionTest (M3574 M5700 M6367 M6777)
So, if you are looking for a mantis number just search for
Mantis and Squeak Tickets:
http://code.google.com/p/pharo/issues/list?can=1&q=label%3AType-Mantis
+OR+label%3AType-Squeak
You get a page with all mantis numbers on it. I think this
way it is not too hard to keep track.
If you have a shell und you love nasty one liners you can do:
wget -O -
"http://code.google.com/p/pharo/issues/list?q=label:Type-Mantis
%20OR%
20label:Type-Squeak&can=1" | perl -ne 'while(m/(M[0-9]+)/g)
{ print "$1
\n"; }' | sort
which outputs:
M2446
M3568
M3574
M4654
M5251
M5392
M5567
M5619
M5641
M5700
M5704
M6070
M6355
M6367
M6402
M6405
M6520
M6702
M6711
M6777
M7090
M7107
hope you like it,
Norbert
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
