On 08/31/2010 10:40 PM, Jeff Spaleta wrote: > On Tue, Aug 31, 2010 at 8:57 AM, Jon Masters <jonathan@xxxxxxxxxxxxxx> wrote: >> Things like Firefox, and Thunderbird have large external teams >> maintaining them who appear to have goals around ensuring a consistent >> user experience, with testing, and so forth, over and above just getting >> new features. They even do self-updating on some platforms, etc. I would >> say they are fantastic examples of packages where you can get away with >> a lower commitment in favor of updating them more frequently because the >> upstream is known to have the user experience interest as a top priority >> over adding new features. But that isn't a given for every single piece >> of software by any means, especially when it comes to upstream testing. > Uhm wait... wasn't a mid release update to thunderbird one of the > historic examples of a large behavior change that precipitated a > strong negative reaction? I think you are careening well away from > fact based argument here. We shipped a Beta or a RC and then toggled on indexing in a post-release update. Upstream is not responsible for that. Package maintainer is. Rahul -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
