FW: [Nexus-developers] API state

[Nick Maliszewskyj]

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

Akeroyd, FA (Freddie) wrote:

>>Slightly off-topic but timely...
>>
>>Mark, Freddy - how do you feel about pushing back the next release
>>a few weeks (say until June 3)? We can ensure that our dependencies
>>on mxml for the XML interface are straightened out and that our
>>autotools setup works in the different configurations we will use.
>>
>>    
>>
>Fine with me, though maybe a 2.1 release as Ray suggested is another
>option as if we are to make some internal changes with attributes it
>would be worth having a stable 2.* base for people. We could just
>exclude XML from the configure script and distribution kit, but leave
>CVS the same 
>
>  
>
>>Freddy - what is the state of the NXU routines?
>>    
>>
>Not finished yet ... maybe by 2/6 but (as usual) depends on what's going
>on (or needs fixing) at ISIS
>
>Freddie
>
>
>
>
>_______________________________________________
>NeXus-developers mailing list
>NeXus-developers at anl.gov
>http://www.neutron.anl.gov/mailman/listinfo/nexus-developers
>
>  
>

-- 
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
o Dr. Nicholas C. Maliszewskyj
o Center for Neutron Research
o National Institute of Standards & Technology
o 100 Bureau Drive, Stop 8562
o Gaithersburg MD 20899-8562
o nickm at nist.gov     Phone: (301)975-3171    Fax: (301)921-9847
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo