FW: [Nexus-developers] API state

[Akeroyd, FA (Freddie)]

I agree that a working XML layer is the priority as it will be a big
boost for potential NeXus use in the ASCII community. I would suggest
aiming for a solid 3.0 without NXU and then release NXU in 3.1 say -
rather than completing NXU now I think it would be more useful for me to
work on things like:
- Tidying up the Bug/enhancement reporting interface
- Making CVS checkins automatically build nexus rpm kits from CVS for
easy installation and testing etc
- Having pre-build hdf + mxml distributions on the NeXus web site to
make installation easier (or maybe we can even bundle hdf + mxml in with
the nexus kit?)

Freddie

P.S. was NXtranslate coming out of "contrib" for the 3.0 release?

-----Original Message-----
From: Nick Maliszewskyj [mailto:nickm at nist.gov] 
Sent: 20 May 2005 17:24
To: Akeroyd, FA (Freddie)
Cc: nexus-developers at anl.gov
Subject: Re: FW: [Nexus-developers] API state

I'm not completely wedded to the requirement of pushing out
3.0 vs. 2.1.  I am concerned, however, about ensuring that
we do get a working XML layer out into usage in the short term.
If a truncated 3.0 (no XML, no NXU, or at least these things
are not compiled and linked in) will pass as a 2.1, then fine.
If much more work is required to build the distribution kit and
to make the necessary tests then we should keep pressing on to
3.0.

We are all busy and subject to the demands of our employers. We
need to release soon, but we need to do so in such a way that
taxes our meager resources least. If we package 2.1, let's do so
with the understanding that 3.0 (beta or not) is right around
the corner.

Nick