Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Release 3.7, freeze on monday

Re: Release 3.7, freeze on monday

From: David Hall <dmhall_at_gmail.com>
Date: Mon, 11 Oct 2010 13:59:50 -0400

On 10/11/2010 01:47 PM, Paul Louden wrote:
> I'd like to propose one additional step - at the time the patch is
> posted on flyspray, the person seeking to have it committed sends an
> email out to the -dev list. Also, if a patch has been on flyspray for
> some time, and has just reached committable status, then they send out
> the email to -dev at that time. The week begins based on when the -dev
> email is sent, rather than when the patch is posted to flyspray, but
> affirmations / objections must be on flyspray (or in one place, but that
> seems the most logical to me at this time) so that they don't need to be
> collected across multiple sources, and so there's a clear record.

As I said (in the wrong place (#rockbox-community)), this proposed
addendum by Llorean achieves what _I_ believe is the crucial component
of this overall proposal, that requested changes to behavior be backed
by supportive structural changes.

--soap
Received on 2010-10-11


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa