bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A Hurd release


From: Leonardo Pereira
Subject: Re: A Hurd release
Date: Wed, 5 Jan 2005 09:21:39 -0800 (PST)


Bas Wijnen <shevek@fmf.nl> wrote:

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.

It has been a very long time since the last release. I think it is a
bad idea to wait for all known bugs (and missing features) to be fixed.
There should be a release soon, so people know we're still working.
If there are bugs of which we know, users should know, preferably before
they encounter them. Of course it's still possible that users run into
things they didn't expect, but we should try to avoid those situations
whenever we can.

Thanks,
Bas

--
I encourage people to send encrypted e-mail (see http://www.gnupg.org).
If you have problems reading my e-mail, use a better reader.
Please send the central message of e-mails as plain text
in the message body, not as HTML and definitely not as MS Word.
Please do not use the MS Word format for attachments either.
For more information, see http://129.125.47.90/e-mail.html


> ATTACHMENT part 1.2 application/pgp-signature name=signature.asc
_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd


 
Why doesn't release the version 0.3 and after that, to doesn't return to that discussion, use the list of thigs that need to be done and after a specified numbers of things from that list was done, a new version is released. This can be a way to show that the project isn't dead, to prevent discussions before every release and to now in what rhythm the project is progressing.


Do you Yahoo!?
The all-new My Yahoo! – Get yours free!
reply via email to

[Prev in Thread] Current Thread [Next in Thread]