<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Re: [development] Severity levels</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText9093 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>For now it should probably go
as a child page here: <A
href="http://drupal.org/node/10259">http://drupal.org/node/10259</A></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>so it doesn't get lost. I am looking
through the developers guide strucutre and trying to figure the best approach
for it. We have some duplicate and even triplicate content that needs
heavy editing and I want to do it it in one fell swoop.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> development-bounces@drupal.org on behalf
of Bčr Kessels<BR><B>Sent:</B> Mon 1/16/2006 8:29 AM<BR><B>To:</B>
development@drupal.org<BR><B>Cc:</B> documentation@drupal.org<BR><B>Subject:</B>
Re: [development] Severity levels<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>This should (also) be discussed on the docs list.<BR><BR>Where
can we put it? IMO a simple bookpage with a link on the issue creation<BR>page
should do, not?<BR><BR>Op maandag 16 januari 2006 17:17, schreef Karoly
Negyesi:<BR>> extreme critical: when a bug breaks all core , sessions,
bootstrap one of <BR>> the form elements or something like that. These
are to be fixed <BR>> immediately because Drupal HEAD is not usable at
all.<BR>><BR>> critical bugs render a whole (or most of a) module
unusable. Example: you <BR>> can't post a forum topic.<BR>><BR>>
major bugs: a smaller part of a module. You can't add a menu with menu
<BR>> module.<BR>><BR>> -- below these are bugs that do not hold
a release --<BR>><BR>> Normal bugs just bugs, we could even release with
these. Just one <BR>> functionality, like the category filter not
working on node admin screen.<BR>Can we release with these? Personally I don't
really care, and woulod say<BR>'yes'. But that is because I work for my cleints
and can filter out therse<BR>bugs before a site goes live. But certainly Joe
Schmoe will get a negative<BR>idea about a piece of software that 'has bogs all
over the place' (I cannot<BR>find the comment IO refer to, anymore). I think
this is up to Dries to<BR>decide, what and how many boogs are still alive when
we go live?<BR><BR>> And minor bugs are cosmetical stuff, notices etc<BR>Are
those not 'tasks' instead. Or even features?<BR><BR>--<BR> PGP
ber@webschuur.com<BR> <A
href="http://www.webschuur.com/sites/webschuur.com/files/ber_webschuur.asc">http://www.webschuur.com/sites/webschuur.com/files/ber_webschuur.asc</A><BR> PGP
berkessels@gmx.net<BR> <A
href="http://www.webschuur.com/sites/webschuur.com/files/ber_gmx.asc">http://www.webschuur.com/sites/webschuur.com/files/ber_gmx.asc</A><BR><BR></FONT></P></DIV>
</BODY>
</HTML>