On Mon, May 24, 2010 at 10:37 AM, Adrian Lienhard <a...@netstyle.ch> wrote:
> Hi Guille and Carla, > > Yes for certain actions you need to be a committer. I added you both. > Please feel free to help maintaining the issue tracker :) > > I don't like this setting. I rather pharo users (not necessary committers) be able to directly tag. Google code doesn't allow us that or it is just our configuration ? Cheers Mariano > If an issue is not clear and lacking information, please add a note and/or > ask in the mailing list. If an issue cannot be reproduced and the creator > does not provide details, we just switch to "won't fix". > > Another area that needs work is to identify which issues should still be > tackled for 1.1. In the tracker we currently have over 200 issues for > milestone 1.1. Many are of the form "we should do X" and are not critical > for the 1.1 release. Others may be show stopper bugs that need to be fixed. > Identifying the latter is important. > > Cheers, > Adrian > > On May 24, 2010, at 07:10 , Carla F. Griggio wrote: > > > Hmm... if I wanted to change the status of an issue to Fixed (for > example), > > I think I'm not able to do that either. Are you? > > > > Should we be commiters to be able to do these things? > > > > On Mon, May 24, 2010 at 2:04 AM, Carla F. Griggio > > <carla.grig...@gmail.com>wrote: > > > >> Welcome, Guille :) It was very cool to have you in the Sprint :) > >> > >> I notice that if I try to post a new issue, I can't categorize it. Who > is > >> able to categorize issues? > >> > >> Carla. > >> > >> 2010/5/23 Guillermo Polito <guillermopol...@gmail.com> > >> > >>> Hi! > >>> > >>> First I may introduce myself. My name is Guillermo Polito and I'm from > >>> Argentina. I've been using Pharo for several months with some > colleagues > >>> that are already here to teach OOP in the UTN university, and i've been > >>> suscribed to this mailing list for some time. But it's my first mail > here > >>> :P. > >>> > >>> I participated yesterday in the Pharo Sprint in Argentina and there I > had > >>> my first look at the issue tracker. And well, it seemed to me to be a > >>> little messy. There are lots of issues that aren't properly explained, > some > >>> of them are duplicated, and they are not well organized. > >>> It would be nice to use the labels googlecode provides to give them > some > >>> categorization, so we can browse them in a more intelligent way. Maybe > we > >>> can split the issues in "modules" (like Collection issues, Compiler > Issues, > >>> Closures Issues, Networking Issues...) or something like that. That > will > >>> help in avoiding duplications and looking for issues to solve (because > I can > >>> look for issues in the modules I know the most). > >>> > >>> At the moment I will stay looking for issues i can fix or commenting > the > >>> ones that lacks information :). > >>> > >>> Regards, > >>> Guille > >>> > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project@lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >> > >> > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project@lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
