On Wed, 2008-06-25 at 09:54 +0200, Stéphane Ducasse wrote:
> yes
> I'm just losing time because sometimes there is not enough information  
> for me.
> So may be we should have a wiki so that I can follow what I should  
> integrate.
> 
As this is the inbox everything should be treated until it is
empty. I thought this was the reason for TreatedInbox.

We could do a SLICE for every fix so you could see what needs
to be updated. But then it is hard to be sure someone reviewed
it.

Maybe the best solution is to use the issue tracker on google.
That's the purpose it serves. If someone has an update he can
open a ticket with type "patch" and status "Fixed". If another
one has reviewed it he can change the status to "verified". To
see what is ready for update you just filter the issues by 
status "Verified"

Norbert
> Stef
> 
> On Jun 25, 2008, at 9:45 AM, Norbert Hartl wrote:
> 
> > Are you going to harvest the rest of the packages, too?
> >
> > KernelTests-al.67
> > Monticello-al.319
> >
> > are fixing all but 2 remaining tests.
> > Norbert
> >
> > On Wed, 2008-06-25 at 09:00 +0200, Stéphane Ducasse wrote:
> >> this is strange when I do a merge with SLICE-randomRemoval I get an
> >> emtpy list.
> >> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval  
> >> the
> >> same?
> >> Should I close SLICE-randomRemoval?
> >
> >> Stef
> >>
> >> On Jun 25, 2008, at 8:52 AM, Stéphane Ducasse wrote:
> >>
> >>> Hi all
> >>>
> >>> I got some funny unpublished packages and I'm a bit confused. So
> >>> could you check what I did.
> >>> I was harvesting MVC removal + norbert cleaning SLICE-
> >>> UnimplementedCallsFix1-NorbertHartl.1
> >>>
> >>> I have to find some time (argh) to improve the process and the
> >>> tools. because this is far too much manual.
> >>>
> >>> Stef
> >>>
> >>> _______________________________________________
> >>> 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

Reply via email to