July 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Bug tracker (was 3dot10 fixes)

by Serge Stinckwich

We just change the issue tool, so we don't want to change again right now. I think we could change in the future, when we want a complete self-hosting issue tracker. 2008/7/2 Norbert Hartl <norbert(a)hartl.name>: > On Wed, 2008-07-02 at 10:48 +0200, Adrian Lienhard wrote: >> Hi Janko, >> >> On Jul 2, 2008, at 10:27 , Janko MivÅ¡ek wrote: >> >> > Adrian Lienhard wrote: >> >> Matthew, we decided to use Google code instead of Mantis or another >> >> bug tracker. >> >> All systems have their pros and cons, but personally I like Google >> >> code, and that's what we are using now. >> > >> > What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas >> > Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr >> > . Besides issue tracker there is also a Wiki and repository browser. >> >> I do not find an issue tracker on http://scribo.bioskop.fr. Have I >> missed something? >> >> > SPM is still in development but with more usage I'm sure Nicolas >> > will speed up work. But comparing with Google Code, we are near >> > already, IMHO. What do you think? >> >> I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ >> to Google code and it works fairly well. I think we should >> reconsider this decision at a later point. >> > +1 > > Changing again would be pure pain :) And the tool doesn't really > matter if you get it done. It's the people using it. > > Norbert > >> Adrian >> >> > >> > >> > Janko >> > >> > >> >> On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote: >> >>> On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote: >> >>>> I'm starting to dislike google code. >> >>> >> >>> on bugs.squeak.org, there is a project named Pharo. Stef is >> >>> probably the administrator. >> >>> >> >>> I'm sure you know how to use mantis >> >>> >> >>> --Matthew Fulmer -- http://mtfulmer.wordpress.com/ >> > >> > >> > -- >> > Janko MivÅ¡ek >> > Svetovalec za informatiko >> > Eranova d.o.o. >> > Ljubljana, Slovenija >> > www.eranova.si >> > tel: 01 514 22 55 >> > faks: 01 514 22 56 >> > gsm: 031 674 565 >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

July 2, 2008

Re: [Pharo-project] 3dot10 issues

by Norbert Hartl

On Wed, 2008-07-02 at 10:57 +0200, Norbert Hartl wrote: > On Wed, 2008-07-02 at 10:51 +0200, Adrian Lienhard wrote: > > Cool, thanks. > > > > On Jul 2, 2008, at 10:43 , Norbert Hartl wrote: > > > > > I have created issues for all of the fixes mentioned on > > > > > > http://code.google.com/p/pharo/wiki/ThreeDotTenFixes > > > > > > After that I scanned the numbering (I chose the summary to include > > > the number at beginning for sorting) and closed to gaps. The gaps > > > have type comment and appear on the open issues list. I didn't take > > > the time to scan mantis for the mantis number which includes the > > > fix. We can arrange that. > > > > > > All issues have "Type-Squeak" being source of a squeak version fix > > > and "Fixed" as a status. My proposal is that everyone takes tickets > > > produces slices from it and changes the status to verified after > > > uploading. > > > > Unless the fix is trivial , I would still follow the normal process > > and first set the state to Fixed and then have somebody else verify > > the change. > > > Yes, i thought about this. But then this issues are already fixes > and the person that incorporates them is not the author of the > fix. Therefor it is already a fix and the reviewing/slicing is > a verification. But I understand what you mean. Shall I set all > stati to new? That would have the opportunity that they appear in > the open issues list. > Aehem, I changed it already. There is a bulk edit.. option in the issue tracker so this was only a handful of clicks. Very cool! So all are new. So the purity of the process is been kept :) Norbert > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2008

Re: [Pharo-project] 3dot10 issues

by Norbert Hartl

On Wed, 2008-07-02 at 10:51 +0200, Adrian Lienhard wrote: > Cool, thanks. > > On Jul 2, 2008, at 10:43 , Norbert Hartl wrote: > > > I have created issues for all of the fixes mentioned on > > > > http://code.google.com/p/pharo/wiki/ThreeDotTenFixes > > > > After that I scanned the numbering (I chose the summary to include > > the number at beginning for sorting) and closed to gaps. The gaps > > have type comment and appear on the open issues list. I didn't take > > the time to scan mantis for the mantis number which includes the > > fix. We can arrange that. > > > > All issues have "Type-Squeak" being source of a squeak version fix > > and "Fixed" as a status. My proposal is that everyone takes tickets > > produces slices from it and changes the status to verified after > > uploading. > > Unless the fix is trivial , I would still follow the normal process > and first set the state to Fixed and then have somebody else verify > the change. > Yes, i thought about this. But then this issues are already fixes and the person that incorporates them is not the author of the fix. Therefor it is already a fix and the reviewing/slicing is a verification. But I understand what you mean. Shall I set all stati to new? That would have the opportunity that they appear in the open issues list. Norbert

July 2, 2008

Re: [Pharo-project] Bug tracker (was 3dot10 fixes)

by Norbert Hartl

On Wed, 2008-07-02 at 10:48 +0200, Adrian Lienhard wrote: > Hi Janko, > > On Jul 2, 2008, at 10:27 , Janko MivÅ¡ek wrote: > > > Adrian Lienhard wrote: > >> Matthew, we decided to use Google code instead of Mantis or another > >> bug tracker. > >> All systems have their pros and cons, but personally I like Google > >> code, and that's what we are using now. > > > > What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas > > Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr > > . Besides issue tracker there is also a Wiki and repository browser. > > I do not find an issue tracker on http://scribo.bioskop.fr. Have I > missed something? > > > SPM is still in development but with more usage I'm sure Nicolas > > will speed up work. But comparing with Google Code, we are near > > already, IMHO. What do you think? > > I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ > to Google code and it works fairly well. I think we should > reconsider this decision at a later point. > +1 Changing again would be pure pain :) And the tool doesn't really matter if you get it done. It's the people using it. Norbert > Adrian > > > > > > > Janko > > > > > >> On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote: > >>> On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote: > >>>> I'm starting to dislike google code. > >>> > >>> on bugs.squeak.org, there is a project named Pharo. Stef is > >>> probably the administrator. > >>> > >>> I'm sure you know how to use mantis > >>> > >>> --Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > > > > > -- > > Janko MivÅ¡ek > > Svetovalec za informatiko > > Eranova d.o.o. > > Ljubljana, Slovenija > > www.eranova.si > > tel: 01 514 22 55 > > faks: 01 514 22 56 > > gsm: 031 674 565 > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2008

Re: [Pharo-project] 3dot10 issues

by Adrian Lienhard

Cool, thanks. On Jul 2, 2008, at 10:43 , Norbert Hartl wrote: > I have created issues for all of the fixes mentioned on > > http://code.google.com/p/pharo/wiki/ThreeDotTenFixes > > After that I scanned the numbering (I chose the summary to include > the number at beginning for sorting) and closed to gaps. The gaps > have type comment and appear on the open issues list. I didn't take > the time to scan mantis for the mantis number which includes the > fix. We can arrange that. > > All issues have "Type-Squeak" being source of a squeak version fix > and "Fixed" as a status. My proposal is that everyone takes tickets > produces slices from it and changes the status to verified after > uploading. Unless the fix is trivial , I would still follow the normal process and first set the state to Fixed and then have somebody else verify the change. Adrian

July 2, 2008

Re: [Pharo-project] 3dot10 issues

by Norbert Hartl

Do we have to check authors and license agreements of every fix? I remember that the 3.10 fixes are subject to legal issues. Is it so? Norbert On Wed, 2008-07-02 at 10:43 +0200, Norbert Hartl wrote: > I have created issues for all of the fixes mentioned on > > http://code.google.com/p/pharo/wiki/ThreeDotTenFixes > > After that I scanned the numbering (I chose the summary to include > the number at beginning for sorting) and closed to gaps. The gaps > have type comment and appear on the open issues list. I didn't take > the time to scan mantis for the mantis number which includes the > fix. We can arrange that. > > All issues have "Type-Squeak" being source of a squeak version fix > and "Fixed" as a status. My proposal is that everyone takes tickets > produces slices from it and changes the status to verified after > uploading. > > To see all issues have a look at: > > http://code.google.com/p/pharo/issues/list?can=1&q=type:Squeak&sort=summary… > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2008

Re: [Pharo-project] Bug tracker (was 3dot10 fixes)

by Adrian Lienhard

Hi Janko, On Jul 2, 2008, at 10:27 , Janko MivÅ¡ek wrote: > Adrian Lienhard wrote: >> Matthew, we decided to use Google code instead of Mantis or another >> bug tracker. >> All systems have their pros and cons, but personally I like Google >> code, and that's what we are using now. > > What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas > Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr > . Besides issue tracker there is also a Wiki and repository browser. I do not find an issue tracker on http://scribo.bioskop.fr. Have I missed something? > SPM is still in development but with more usage I'm sure Nicolas > will speed up work. But comparing with Google Code, we are near > already, IMHO. What do you think? I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ to Google code and it works fairly well. I think we should reconsider this decision at a later point. Adrian > > > Janko > > >> On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote: >>> On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote: >>>> I'm starting to dislike google code. >>> >>> on bugs.squeak.org, there is a project named Pharo. Stef is >>> probably the administrator. >>> >>> I'm sure you know how to use mantis >>> >>> --Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > > -- > Janko MivÅ¡ek > Svetovalec za informatiko > Eranova d.o.o. > Ljubljana, Slovenija > www.eranova.si > tel: 01 514 22 55 > faks: 01 514 22 56 > gsm: 031 674 565 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2008

[Pharo-project] 3dot10 issues

by Norbert Hartl

I have created issues for all of the fixes mentioned on http://code.google.com/p/pharo/wiki/ThreeDotTenFixes After that I scanned the numbering (I chose the summary to include the number at beginning for sorting) and closed to gaps. The gaps have type comment and appear on the open issues list. I didn't take the time to scan mantis for the mantis number which includes the fix. We can arrange that. All issues have "Type-Squeak" being source of a squeak version fix and "Fixed" as a status. My proposal is that everyone takes tickets produces slices from it and changes the status to verified after uploading. To see all issues have a look at: http://code.google.com/p/pharo/issues/list?can=1&q=type:Squeak&sort=summary… Norbert

July 2, 2008

[Pharo-project] Bug tracker (was 3dot10 fixes)

by Janko MivÅ¡ek

Adrian Lienhard wrote: > Matthew, we decided to use Google code instead of Mantis or another bug > tracker. > All systems have their pros and cons, but personally I like Google code, > and that's what we are using now. What about pure Smalltalk SPM (Squeak Project Manager) by Nicolas Petton? See for example SPM for Scribo project: http://scribo.bioskop.fr. Besides issue tracker there is also a Wiki and repository browser. SPM is still in development but with more usage I'm sure Nicolas will speed up work. But comparing with Google Code, we are near already, IMHO. What do you think? Janko > On Jul 2, 2008, at 09:39 , Matthew Fulmer wrote: > >> On Wed, Jul 02, 2008 at 09:29:07AM +0200, Norbert Hartl wrote: >>> I'm starting to dislike google code. >> >> on bugs.squeak.org, there is a project named Pharo. Stef is >> probably the administrator. >> >> I'm sure you know how to use mantis >> >> --Matthew Fulmer -- http://mtfulmer.wordpress.com/ > -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

July 2, 2008

Re: [Pharo-project] need help understanding the issue UI

by StÃ©phane Ducasse

Ok I was idiot. Stef On Jul 2, 2008, at 10:05 AM, Damien Cassou wrote: > On Wed, Jul 2, 2008 at 8:54 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> hi guy >> >> if I go to http://code.google.com/p/pharo/issues/list >> and select all issue I do not see >> >>>>>> http://code.google.com/p/pharo/issues/detail?id=23 >> >> This UI is alienating me. I spent 10 min to try >> How can I see all the issues? >> and not only stopping at 15 >> >> I'm lost.... > > When an issue is closed, it is hidden so that it does not bother you > anymore. Mantis does the same by default. > > -- > 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) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 2, 2008