On Tue, May 02, 2006 at 07:55:53PM +0100, Matthew East wrote: > On Tue, 2006-05-02 at 11:43 -0700, Matt Zimmerman wrote: > > [...] > So, that handles the "changing" part. Not the "seeing" bit though. There > is literally no field which tells the normal user what release has been > targetted, AFAICS.
Yes, that seems like a Malone bug. > > My understanding is that in the future, Malone will incorporate this > > workflow: anyone can "nominate" a bug for a milestone, but an authority must > > confirm it. > > Sounds quite cool, if the authorities have time to deal with all the requests. The alternatives would seem to be: - Keep the current situation (only privileged users can set milestones) - Anyone can set a milestone (this was a nightmare because I had to go around and clean up where people had set milestones incorrectly) - Create a separate privilege level specifically for milestones, add anyone to it who might have a legitimate reason to set a milestone on any package, keep them informed about the relevant policies for milestone settings, etc. - Allow anyone to propose a milestone target, but require confirmation from a privileged user The last of these seems superior to any of the others, regardless of how much time the drivers have. It certainly requires the least of my time. -- - mdz -- launchpad-users mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/launchpad-users
