From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 40951@debbugs.gnu.org
Subject: bug#40951: Weird highlighting
Date: Wed, 29 Apr 2020 08:52:37 +0800 [thread overview]
Message-ID: <87imhj6rl6.8.fsf@jidanni.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 115 bytes --]
Why does the
taking...:
line get different color (bad)
but the
A couple...:
line not? (good).
[pipe to procmail:]
[-- Attachment #2: Type: message/rfc822, Size: 1505 bytes --]
From: Martin Ward <martin@gkc.org.uk>
Subject: Re: How NASA does software testing and QA (Functionize)
Date: Tue, 28 Apr 2020 17:05:17 +0800
Message-ID: <87sggn6rw3.8.fsf@totally-fudged-out-message-id>
A couple of quotes from the article that I found depressing:
> Crumbley recommends the CMMI Institute's Capability Maturity Model
> Integration (CMMI) as a good process model.
CMMI defined five "maturity levels" starting at level 1: "Processes
unpredictable, poorly controlled and reactive."
So to say that you use "CMMI" just means you have decided which maturity
level your process is currently defined as. You could be level 1 and happy
with it!
Crumbley does not say what level NASA's software development department has
currently reached, or what level they are aiming at nor what steps they are
taking to reach the desired level. Instead he says:
> We use the CMMI model as a tool to see how our software development
> practices compare with other industries
"Other industries" have woefully inadequate software development practices:
as exemplified in every issue of comp.risks! Comparing yourself with them
just gives a false sense of security. NASA's software requirements are so
much more stringent than the vast majority of other industries: on other
industries, if the software more-or-less works, only needs rebooting
occasionally and only has a few zero-day exploits per week, then the
software is considered to be a success. He does not even *mention* formal
methods.
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
No such bug when viewed in mutt.
Gnus v5.13
GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.11)
of 2019-09-23, modified by Debian
next reply other threads:[~2020-04-29 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 0:52 積丹尼 Dan Jacobson [this message]
2020-04-29 7:44 ` bug#40951: Weird highlighting Kévin Le Gouguec
2020-04-29 17:50 ` 積丹尼 Dan Jacobson
2020-05-01 18:44 ` Kévin Le Gouguec
2020-08-05 11:19 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imhj6rl6.8.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=40951@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).