From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: Upgrading ConTeXt and testing
Date: Sun, 28 Aug 2005 13:40:42 -0600 [thread overview]
Message-ID: <431B3E5E@webmail.colostate.edu> (raw)
Dear gang,
I understand that ConTeXt is a HUGE system, and it is impossible for Hans to
micro-test everything. However, it is not infrequent that upgrades by users
lead to sometimes days of lost productivity. For example, a recent change in
the indentation code ruined a 425-page manuscript and it took me hours to
identify the source of the problem. And that was only one problem.
Given the problems some of us have faced when upgrading, I think that we
really need a test suite of documents that provide some benchmarks for each
part of the system, from building supported format files to features to
supported output formats. Maybe this would take a long time; but perhaps the
task could be delegated among is. I would be willing to be part of that team
(including but not exclusively the aleph-dvipdfmx cycle).
When a new ConTeXt is released, Taco or someone else could then document which
bugs are fixed, features added, and, most importantly, what features are
changed or broken. That way, upgrading does not always have to be a leap in
the dark with fingers crossed.
The above is just an idea. I hope it can be developed into something actually
workable and useful.
A related point (disussed before) is that ConTeXt needs to become completely
independent of the TeX distributions. mswincontext.zip is a good start (I no
longer use fpTeX), but things like dvipdfmx and the plain format (for testing
purposes) need to be thoroughly supported and tested. Again, a support team
for Hans is needed (especially for Mac OSX and Unix), and I'm willing to help
as far as my skills will allow.
Best
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-08-28 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 19:40 Idris Samawi Hamid [this message]
2005-08-29 9:01 ` Taco Hoekwater
2005-08-29 13:04 ` Hans Hagen
2005-08-29 18:18 ` Brooks Moses
2005-08-30 2:53 ` jjgod
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=431B3E5E@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).