How about using category "cleanup" instead of "bug"? And thank you for your work!
nicolai 2014-02-06 11:16 GMT+01:00 Torsten Bergmann <[email protected]>: > Hi Ben > > if we would just like to increase the number of cases/issues > using a "case per class" would have been better. > Adding final quality improvements (like docu) is usual before releases > not only in the ST world. > > For the reasons: > A single person can only do it step by step and therefore I > used the granularity of projects/packages. This also helps reintegration > /mergin back into external managed parts. > There was no reaction onto my call for action from others. > > So instead of grumbling afterwards better use your keyboard to comment on > classes ;) > > Thx > T. > > > Gesendet: Donnerstag, 06. Februar 2014 um 10:43 Uhr > > Von: [email protected] > > An: "Pharo Development List" <[email protected]> > > Betreff: Re: [Pharo-dev] comments :) > > > > Good work. Minor thing though - could they maybe grouped under one Case. > > I'd hate for someone to look at the massive amount work done for Pharo 3 > > indicated by the cases close and think "Its just lots of comment updates" > > Sure it would end up being a long running case - with a lot of slices > > (each based off the most recent image). You'd have to see how that > > panned out, and itf it got too long, just link to a new case for the > > next group. > > Or maybe there is some difficulty that I can't forsee. > > cheers -ben > > > > Torsten Bergmann wrote: > > > Still 1017 to go. Feel free to help: > > > > > > Smalltalk allClasses select: [:each | each comment > includesSubstring: 'xxxx' ] > > > > > > External Package owners should also reintegrate too so these do not > > > get lost when a new version of external packages get integrated. > > > (for instance https://pharo.fogbugz.com/f/cases/12812 for Spec) > > > > > > step by step it goes ... > > > > > > Bye > > > T. > > > > > > > > > Gesendet: Mittwoch, 05. Februar 2014 um 08:36 Uhr > > > Von: Pharo4Stef <[email protected]> > > > An: "Pharo Development List" <[email protected]> > > > Betreff: [Pharo-dev] comments :) > > > > > > Thanks for all these comments! > > > > > > > > > On 05 Feb 2014, at 00:27, GitHub <[email protected]> wrote: 30742 > > > 12794 Class comments missing in UpdateStreamer package > > > > https://pharo.fogbugz.com/f/cases/12794[https://pharo.fogbugz.com/f/cases/12794] > > > > > > 12802 Class comments missing for Kernel package > > > > https://pharo.fogbugz.com/f/cases/12802[https://pharo.fogbugz.com/f/cases/12802] > > > > > > 12804 Class comment missing in AST packages > > > > https://pharo.fogbugz.com/f/cases/12804[https://pharo.fogbugz.com/f/cases/12804] > > > > > > 12797 Class comments missing for tools package > > > > https://pharo.fogbugz.com/f/cases/12797[https://pharo.fogbugz.com/f/cases/12797] > > > > > > 12796 Class comments missing for Traits package > > > > https://pharo.fogbugz.com/f/cases/12796[https://pharo.fogbugz.com/f/cases/12796] > > > > > > 12798 Class comments missing in GroupManager package > > > > https://pharo.fogbugz.com/f/cases/12798[https://pharo.fogbugz.com/f/cases/12798] > > > > > > 12806 Class comment missing in package FreeType + categorizing for > FreeTypeCacheTest > > > > https://pharo.fogbugz.com/f/cases/12806[https://pharo.fogbugz.com/f/cases/12806] > > > > > > 12800 EyeContextInspector should be renamed to > EyeMethodContextInspector > > > > https://pharo.fogbugz.com/f/cases/12800[https://pharo.fogbugz.com/f/cases/12800] > > > > > > > > > > > > > > > > >
