From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
In-Reply-To: <200705281853.28124.dgollub@suse.de>
References: <1180273950.15368.42.camel@gilboa-work-dev.localdomain>
	<200705280119.47962.dgollub@suse.de>
	<1180340996.21432.90.camel@aeonflux.holtmann.net>
	<200705281853.28124.dgollub@suse.de>
Date: Tue, 29 May 2007 05:50:53 +0200
Message-Id: <1180410653.21432.106.camel@aeonflux.holtmann.net>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] Suggesting bluez_pinhelper
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Hi Daniel,

> > please do releases and do them often. It is important to have releases,
> > because otherwise nobody really tests the code. Trust me on that one.
> > Only core developers check out the source from the SCM directly.
> 
> That's true...
> 
> I run out of time will hacking on kdebluetooth for KDE3 and KDE4 (and other 
> projects) at the same time. I try to replace the kdebluetooth trunk version 
> with the kdebluetooth-dbus-integration branch the next days.

sometimes a broken release is better than no release. However you need
to be prepared to fix it as soon as possible. So following release early
and release often might help to get this progressing faster.

Regards

Marcel


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel