Bug#242117: cabot: Sucess report

[Laurent Fousse]

--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Rudy,

* Rudy Godoy [2004-07-16]:
>=20
> Hi, I'been using cabot for almost two years, and in that time I haven't
> faced any problem.

Nice to hear that :-)

> So I don't see a reason to stop it from enter testing, in the other
> hand I'm not sure if a "sucessful report" it's a proper use of BTS.

Given the subject of this bug, I think this is a proper use, yes.

About the bug itself, I trusted upstream about the fact cabot was not
ready for `testing' yet. From my own experience of some keysignings
where I used cabot and I saw some other people use it too, I think the
actual testing of the package is rather satisfactory.

But we had some items on the TODO list that were considered important
before cabot could enter `testing' (well, some items are resolved).

If you want to help with them, or want to convince upstream these are
not showstopper for testing, please do so (in the cabot-devel list,
put in Cc) :-)

> As I understand unless there are really serious problems reported which
> are making software unusable, it should be tagged as RC.

This was rather "we would not be comfortable with this version in a
stable release for the moment". There are quite some bugs of this
nature in the BTS, and I think we should trust upstreams when it comes
to usability in the long run.

Peter, Joost, can you remember which points are top priority in the
TODO list? I think we have a volunteer here ;-)

Regards,

Laurent.

--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA962yRoAVF6FpbSsRAk4/AKCK712ws3mOEKbfKNppFbUkxb7cugCeL2Wj
29+V4u3HmgqcuFQXePRB5EE=
=0H/l
-----END PGP SIGNATURE-----

--wRRV7LY7NUeQGEoC--