[Axiom-developer] Literate Programming

[daly]

Martin,

> I will propose a model I could live with on friday morning.

And hopefully on the following monday :-)

I'm open to suggestion, especially if it smooths the working
environment. I've been trying to get the SVN running smoothly
by ensuring that every update is a changeset, that is, a single
logical change that adds a feature or fixes a bug. And I've been
marking either the bugzilla bug number or the SVN revision number
in the changelog entry.

Every patch has extensive testing here before anything actually
shows up in SVN. Posted patches, for instance the ones that Stephen
has been posting, usually get modified or expanded (e.g. to add 
the files to the Makefile chain, to rearrange documentation, etc).
Each patch requires at least two builds, a pre-patch build and a
post-patch build so any changes can be identified. Thus there is a
bit of lag from the time the patch hits the mailing list and the
time the patch hits SVN. In some cases, e.g. the first defintrf
patch, the posted patch never makes it thru testing at all.

This may seem like overkill, especially since people have already
tested their patch before posting it. However, the silver branch
should never be broken (modulo mistakes). Its a quality issue.

I realize I've been a bit of a pompous ass and I do apologize
for exposing my fundamental character so clearly in public :-)

Seriously though, I hope you can accept my apology.

Tim