|
From: | Brad |
Subject: | Re: [Gnash-dev] Re: pre-release candidate |
Date: | Tue, 08 Feb 2011 21:11:20 -0500 |
User-agent: | Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 |
On 08/02/11 8:56 PM, Rob Savoye wrote:
Bugs should be fixed before the code freeze, that's how the process is supposed to work. Just cause I'm the one that makes the release, doesn't mean I'm the one that has to fix all the bugs. I did go through the bug tracker when starting the code freeze, it's just that I wasn't going to launch off and try to fix them all during the release process. Supposedly I'm not the only Gnash developer, although when doing a release, it sure feels like it... - rob -
I wasn't saying you should be the one fixing the bugs and the only one. But someone was advocating making a release without taking the bugs within the bug tracker into consideration before cutting the release.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
[Prev in Thread] | Current Thread | [Next in Thread] |