Skip to content

Rhaptos Software Development

Personal tools
You are here: Home » Developer Blog » Brent's Blog » Progress towards release

Progress towards release Progress towards release

Document Actions
Submitted by brentmh. on 2005-07-11 09:05. Development
Almost there....so close!

Delays

The recent incident right before Ross went on vacation set our schedule back a bit.  Everyone should have to spend a week doing system admin tasks to gain a greater appreciation of how much of your time they can absorb.  I still don't quite have Brian's machine back to full functionality and the staff home directory backups aren't 100% either.  Fortunately Ross gets back this week.

Progress

In the month since I first posted about the upcoming open-source release we've made great progress completing the list.  In fact, every one of the required items has been completed.  We set up one of the new blade servers for testing and things seem to be going well.  The most common type of bugs turning up are security settings that we made in the ZMI but apparently never scripted for new site setup.  Easily found and easily fixed.

I'm also making progress on what turned out to be a big ticket item that didn't make it on my list.  Emmanuel Pietriga, the author of the mathmlc2p.xsl stylesheet we use to transform content MathML into presentation MathML, has agreed to release a new version under the LGPL.  This is wonderful news for us since we use a heavily modified copy and would like to redistribute our changes.  Unfortunately that file has been through a long and contorted history in our repository and splitting out the changes Emmanuel might be interested in including is long tedious work.  I'm down to creating the last few patches, though, so that should be done today or tomorrow.  One good thing to come out of this is that I'm doing cleanups as I go so the result should be nicer code than we've ever had (what were we thinking on some of those changes??)

What's left

  • finishing splitting out mathmlc2p.xsl changes into patches
  • figure out a way to package help files with release
  • put license information in all release files
  • write READMEs for all packages
  • improve installation instructions
  • put out a beta and have some people test the install