Stéphane Ducasse wrote: > > Right now we have milestone1.0 and milestone1.1 for the fixes that are > integrated in both > But indeed we could have a specific tags. > > Stef >>> >>> >> Is it possible to add a new status in Google Code, of Closed-KPF-1.0? >> Then Closed means it was fixed and retrofitted to 1.0. Closed-KPF-1.0 >> means >> fixed only in 1.1alpha. >> Making the KPF list becomes trivial. >> And it also captures the knowledge of whether the issue applied to 1.0 at >> the time of closing, rather than someone have to puzzle over it when >> making >> a release. >> ...Stan >> > >
So would: http://code.google.com/p/pharo/issues/list?can=1&q=Type:Defect,ReportDefect++Milestone:1.1+Status:closed+++-Milestone:1.0&sort=type&colspec=ID+Type+Status+Summary+Milestone+Closed http://code.google.com/p/pharo/issues/list?can=1&q=Type:Defect,ReportDefect++Milestone:1.1+Status:closed+++-Milestone:1.0&sort=type&colspec=ID+Type+Status+Summary+Milestone+Closed Be the KPF IFF the type and status and milestone fields were maintained? -- View this message in context: http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-support-the-creation-of-new-method-cat-tp4194364p4208958.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
