seems like it works, so by default the pharo-internal projects will have the Area "1. Pharo Image" set.
Why the "1."? Well I cannot order the Areas, and the first one is selected by default :P The filter "review" and "integration" now only look at issues that have the proper Area set. On 2013-10-06, at 08:08, Stéphane Ducasse <stephane.duca...@inria.fr> wrote: > thanks! > This is a good idea. > > On Oct 6, 2013, at 1:57 AM, Camillo Bruni <camillobr...@gmail.com> wrote: > >>>> I think it should just be fine if we define a different workflow (and thus >>>> different labels) for external projects... >>>> >>>> >>> The 'Area' field looks unused, having only a single option 'Misc'. Perhaps >>> that could be 'Image' and 'External Project' or similar. Most of an >>> external project's issues would also have an area of 'External 'Project', >>> but sometimes it might be 'Image' if a change there is required to fix an >>> issue reported on a project. Or maybe for external projects you have >>> only a single option 'External Project' for Area. >> >> So we need to have 2 things >> 1. a separate project for each external project that wants to report >> 2. a separate Area for these external projects >> >> For instance, NativeBoost has both a stable version in the image and a >> development >> version aside. So if a bug appears in the image we can set the Area to >> "Pharo Image" (the default). >> However, if the bug concerns the development version we set the Area to >> something project >> specific. >> >> I will try to update the tracker and the filters to reflect that... > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
