On Tue, Sep 11, 2012 at 10:20 PM, Graham Binns <gra...@canonical.com> wrote: > On 11 September 2012 11:00, John Arbash Meinel <j...@arbash-meinel.com> wrote: >> I will say that people have different levels of competency (and care) >> to drive a fix all the way through to a full release. So if you make >> the barrier "To do any change, you must drive it through to a full >> release", could make the barrier for drive-by fixes a bit too high. > > Good point. In that case, maybe the person that gets nagged should be > the owner of the project (usually the CE team) or the bug supervisor > (usually ~launchpad-security). > >> I suppose this depends mostly on things that are sourcecode level >> changes, because if it is an egg, you at least need to cut a tarball, >> right? > > I would have thought so, yes.
Interesting data on this topic: lazr.restfulclient had 3 fix committed bugs. All were actually released, just stale metadata. ~All the milestones in the project were still active so choosing a milestone was -hard-. I've dug up the right releases, associated the bugs appropriate, and marked all the milestones except 0.14.0 (which is unreleased) as 'inactive' so they don't show up in pick-lists anymore. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
