From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christian <evilninja@gmx.net>
Subject: Re: new reiser4progs?
Date: Fri, 18 Feb 2005 17:43:19 +0100
Message-ID: <42161B27.9040408@gmx.net>
References: <20050218083158.GA28563@xs4all.nl> <200502181619.59336.vitaly@namesys.com> <20050218140824.GA50286@xs4all.nl> <200502181717.30090.vitaly@namesys.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <200502181717.30090.vitaly@namesys.com>
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: reiserfs-list@namesys.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vitaly Fertman wrote:
> testing a release candidate before releasing.
> the amount of time needed depends on the amount of problems
> appeared, if debugging/fixing/bugfix testing is need, etc.

would it be an option to publish daily (nightly) builds, along with a big.
fat UNTESTED warning? it could be done via scripts and even if it does not
build one day or the other - users would notice that and could report.

thanks,
Christian.
- --
BOFH excuse #88:

Boss' kid fucked up the machine
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCFhsmC/PVm5+NVoYRAnoJAJsFDRGMwm4B6cJcSvKse9vlO0D+KACg74Vx
bA/rsyNUcZk5SPplUFkDXYs=
=41fL
-----END PGP SIGNATURE-----