On Thu, 2009-06-04 at 22:53 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > If, say, the bug is in a package that gets frequent releases, and was > > filed on the development release, you can just use CLOSED UPSTREAM, > > because you can rely on the fact that there'll be a new upstream release > > of the package soon after the upstream report is fixed, you (the > > maintainer) will then naturally package the new release, and the fix for > > the bug will have been rolled into the distribution package without you > > having to do anything besides your normal packaging work. > > In fact that's what happens with KDE, bugfix releases come out once a month > in most cases (the time from the last bugfix point release to the next > feature release is a bit longer though, about 2 months upstream (blame the > folks who decided *.5 releases are not needed), plus about 2 weeks of > testing in updates-testing to prevent regressions). Indeed, KDE would be exactly the kind of project I had in mind for that scenario: it's very actively maintained and bugfix releases show up and are packaged into Fedora frequently. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
