Le dim. 26 mai 2019 à 21:38, Nyall Dawson <[email protected]> a écrit :
> On Mon, 27 May 2019 at 11:43, Denis Rouzaud <[email protected]> > wrote: > > > +1. But, we should indeed have a strict definition of when adding the > milestone (someone is taking care of the fix or every time it's just > considered as important). I'd rather keep milestones for PRs and maybe > bring back the idea of "blocker" tag. > > I think it should only be defined by someone actually assigned to the > bug. E.g. if I self-assign a bunch of bugs I'm actively working on, > I'd like to be able to use milestones to self-manage these... > I see, I'm just afraid to see too many issues left-open with a past milestone. But we can give it a try I guess. > > Nyall > > > >> > >> > >> Nyall > >> > >> * Ideally, we'd block non-core-contributors from setting milestones > >> for issues, to avoid reporters just tagging their issue with an > >> upcoming milestone as a rude way of saying "fix my stuff for me" > >> _______________________________________________ > >> QGIS-Developer mailing list > >> [email protected] > >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
