From mint-bounce@lists.fishpool.fi Thu May 7 05:13:06 2009 Subject: Re: [MiNT] Current FreeMiNT kernel version From: Petr Stehlik To: Frank Naumann Cc: mint@lists.fishpool.fi In-Reply-To: References: <49FE1178.2010800@centrum.cz> <20090506113056.ce8obm7g3vo8osk0@pop.freeola.net> <1241607458.4507.21.camel@petr> Content-Type: text/plain; charset="ISO-8859-2" Date: Thu, 07 May 2009 11:10:45 +0200 Message-Id: <1241687445.20299.10.camel@petr> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pstehlik@sophics.cz Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n479D53I007844 Frank Naumann píše v Čt 07. 05. 2009 v 10:40 +0200: > Hello! > > > Anybody can build the CVS but only Frank (?) can do a proper release. > > Hehe, why do you think so? Because I know what proper release requires thus I know that there are not many people that can do that. I also believe that releases should be done by somebody who leads the particular project and decides what to do, when, and how to do that. And I felt like you were the FreeMiNT leader. Maybe all that's needed now is to say that everything that could be done in FreeMiNT was done already and that the volunteer you ask for would just need to ensure that everything is in place, build and test the binaries, document the changes since last release, make sure that the API and similar documentation still matches the reality in source code, write release notes, pack it all together, upload to web and update the web pages. Petr