From mint-bounce@lists.fishpool.fi Mon May 31 14:38:33 2010 X-Authority-Analysis: v=1.0 c=1 a=XyF7bEpsXVwA:10 a=ADBQPqJMlbwA:10 a=8nJEP1OIZ-IA:10 a=WHrLxatjGjCSoSn2Nh4A:9 a=7siNc1cOcGYZBJxA7ixgI0CBgxkA:4 a=wPNLvfGTeEIA:10 Message-ID: <4C0401A1.7070500@charter.net> Date: Mon, 31 May 2010 14:36:17 -0400 From: Rob Mahlert User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] to release or not to release References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: rmahlert@charter.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On 5/30/2010 4:49 PM, Keith Scroggins wrote: > Hello Helmut, > > While I can not speak to the status of the kernel itself, maybe > between you and Alan, you can decide on a release? I think this is best. Those 2 know best for the state of the kernel. > > What I would do is possibly branch your kernel code for release, not > sure if you want to work with Alan to remerge into trunk, and then > release a test version, and then after X days do a release. Fixes > only into the branch. > > Xaaes might be a little trickier, I am guessing it will take more > time. Alan did mention folding it into trunk as well. > > Keith > I think Helmut's changes should be merged into the trunk. Then a new beta release for bug fixes.. Just my 2 cents. Rob