I think that a list of user visible bugs is a good idea, not compiling a list of what works, and what doesn't helps more people than just newbies. Releasing something that's buggy where the developers don't realize it, makes it aggravating. At lease with a bug list, it cuts down on the confusion. With a bug list, people know what to expect.
On Wed, 2005-01-05 at 12:06 +0100, Alfred M. Szmidt wrote: > If someone is Hurd newbie and (s)he tries to use fakeroot for > building Debian packages, what do you think that (s)he'll think > about the Hurd? > > What will the newbie think if she/head finds a totally obscure bug > that eats the file-system, or any other horrible thing? I think that > you don't really have a point here. > > Bugs exist, if a user finds them they should report them so that they > can be fixed. Doesn't matter if it is a newbie, or a guru. > > a top-level file BUGS that lists major user-visible known bugs. > > That is like "it is not a bug, it is a feature", known bugs should be > fixed before a release. > > > _______________________________________________ > Bug-hurd mailing list > Bug-hurd@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-hurd > _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
